Skip to content

Conversation

@christopherfujino
Copy link
Contributor

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 causing smoke_catalina_hot_mode_dev_cycle__benchmark devicelab test to be flaky.

@fluttergithubbot
Copy link
Contributor

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.

@fluttergithubbot fluttergithubbot added the c: contributor-productivity Team-specific productivity, code health, technical debt. label Aug 29, 2019
Copy link
Contributor

@digiter digiter left a 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.

@christopherfujino
Copy link
Contributor Author

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

@digiter
Copy link
Contributor

digiter commented Aug 29, 2019

But chmod a+x will give executable bit to all of owner/group/other.

@christopherfujino
Copy link
Contributor Author

But chmod a+x will give executable bit to all of owner/group/other.

oh, good point

@christopherfujino
Copy link
Contributor Author

landing on red to fix hot_mode_dev_cycle__benchmark

@christopherfujino christopherfujino merged commit 8ec2c58 into flutter:master Aug 30, 2019
@christopherfujino christopherfujino deleted the fix-devicelab-gradlew branch August 30, 2019 21:13
christopherfujino added a commit that referenced this pull request Aug 30, 2019
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 4, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

c: contributor-productivity Team-specific productivity, code health, technical debt.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants