-
Notifications
You must be signed in to change notification settings - Fork 29.7k
fix recursiveCopy to preserve executable bit #39505
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
fix recursiveCopy to preserve executable bit #39505
Conversation
|
It looks like this pull request may not have tests. Please make sure to add tests before merging. While there are exceptions to this rule, if this patch modifies code it is probably not an exception. Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. |
digiter
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, although I'd prefer keeping the same file mode as the original, as it's a surprise to see more executable bits after copying.
We only add the executable bit to the copied file if the source file had it |
|
But chmod a+x will give executable bit to all of owner/group/other. |
oh, good point |
01c5ae3 to
310ccaf
Compare
|
landing on red to fix |
This reverts commit 8ec2c58.
Description
Copying the fix from this PR to
gradle.dart#311, the recursive copying should check if the target file had the executable bit set, and then make the copied file executable. This was causingsmoke_catalina_hot_mode_dev_cycle__benchmarkdevicelab test to be flaky.