Ignore symlinks when fixing permissions during artifacts tests #1721
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When doing Artifact tests, we need to be resilient to strange umasks
that we have inherited from our environment, screwing up git tree hash
calculations. To do this, we have a
walkdir()
->chmod()
wrapperfunction that started setting permissions on what it thought were files
(due to the fixed
follow_symlink == false
behavior inJuliaLang/julia#35006) but were actually
directories. This caused
chmod()
to apply0o664
permissions todirectories, which were then inaccessible to
rm()
as it tried todelete them.
This fixes #1716