Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove stale contrib files #38970

Merged
merged 1 commit into from
Dec 23, 2020
Merged

Remove stale contrib files #38970

merged 1 commit into from
Dec 23, 2020

Conversation

musm
Copy link
Contributor

@musm musm commented Dec 23, 2020

fixup-libstdc++ isn't being used anymore as well, is BB perhaps using this or is it also safe to remove?

@staticfloat
Copy link
Sponsor Member

Let's not remove it just yet; I may need it in 1.7. If not, we can remove it then.

@staticfloat staticfloat merged commit 0e15141 into JuliaLang:master Dec 23, 2020
@musm musm deleted the del branch December 23, 2020 07:18
@musm
Copy link
Contributor Author

musm commented Dec 23, 2020

Win 32 failure looks odd

@staticfloat
Copy link
Sponsor Member

It's a network failure, don't worry too much about it.

ElOceanografo pushed a commit to ElOceanografo/julia that referenced this pull request May 4, 2021
@garrison
Copy link
Sponsor Member

garrison commented Nov 30, 2021

Why was valgrind-julia.supp deemed to be stale? It is still referenced in the Valgrind devdocs.

EDIT: I just ran under valgrind with no suppression file, and I did not see the single warning that appeared in that suppression file, so maybe it is indeed no longer necessary...

garrison added a commit to garrison/julia that referenced this pull request Dec 3, 2021
contrib/valgrind-julia.supp was removed in JuliaLang#38970, but it is still referenced
[in the Valgrind devdocs](https://docs.julialang.org/en/v1/devdocs/valgrind/).
Either the file should be restored, or the reference should be removed
from the documentation.

Here, I have chosen the option of restoring the file, as I think it
provides some value.  I have also updated it such that it does indeed
suppress the warning (JuliaLang#4533) on the latest master.
@garrison
Copy link
Sponsor Member

garrison commented Dec 3, 2021

I have opened a PR that brings back (an updated version of) valgrind-julia.supp. Feel free to chime in there (#43319) if you would prefer that this file go away permanently.

LilithHafner pushed a commit to LilithHafner/julia that referenced this pull request Feb 22, 2022
contrib/valgrind-julia.supp was removed in JuliaLang#38970, but it is still referenced
[in the Valgrind devdocs](https://docs.julialang.org/en/v1/devdocs/valgrind/).
Either the file should be restored, or the reference should be removed
from the documentation.

Here, I have chosen the option of restoring the file, as I think it
provides some value.  I have also updated it such that it does indeed
suppress the warning (JuliaLang#4533) on the latest master.
LilithHafner pushed a commit to LilithHafner/julia that referenced this pull request Mar 8, 2022
contrib/valgrind-julia.supp was removed in JuliaLang#38970, but it is still referenced
[in the Valgrind devdocs](https://docs.julialang.org/en/v1/devdocs/valgrind/).
Either the file should be restored, or the reference should be removed
from the documentation.

Here, I have chosen the option of restoring the file, as I think it
provides some value.  I have also updated it such that it does indeed
suppress the warning (JuliaLang#4533) on the latest master.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants