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

Reset git tree after first yapf failure #230

Merged
merged 2 commits into from
Jan 10, 2024

Conversation

pbchekin
Copy link
Contributor

We have to run yapf twice because in a clean environment the first run most likely fails because of the race condition in yapf, see google/yapf#1164. If, however, the first run was successful and yapf has modified files, then we need to reset the changes, so the second run can detect them again.

Note that the whole block (ignore the first run and reset the tree) will not be necessary and will be removed after fixed
google/yapf#1164.

We have to run yapf twice because in a clean environment the first run
most likely fails because of the race condition in yapf, see
google/yapf#1164. If, however, the first run
was successful and yapf has modified files, then we need to reset the
changes, so the second run can detect them again.

Note that the whole block (ignore the first run and reset the tree) will
not be necessary and will be removed after fixed
google/yapf#1164.
@pbchekin pbchekin marked this pull request as ready for review January 10, 2024 19:22
@whitneywhtsang whitneywhtsang merged commit 1f3a9b8 into llvm-target Jan 10, 2024
3 checks passed
@whitneywhtsang whitneywhtsang deleted the fix-pre-commit-yapf branch January 10, 2024 19:54
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.

2 participants