-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Revert "[chore] Use crosslink tidylist
in make gotidy
(#37142)"
#37173
Revert "[chore] Use crosslink tidylist
in make gotidy
(#37142)"
#37173
Conversation
…etry#37142)" This reverts commit bc20ac9.
Could you point to a PR which shows non-deterministic behavior? As in, multiple runs of the CI where |
@jade-guiton-dd #37172 is an example. The CI is failing, telling me to run |
@TylerHelmuth Do you have untracked changes to any |
No |
I see. In that case, it does sound like it's non-deterministic (or maybe platform-dependent). |
I'm wondering if different go versions affect it. Can you keep working on a fix? I would love not to need to run |
Yes, I'll work on a fix tomorrow, a revert is fine in the meantime. Could you tell me what OS and version of Go you're using (the one used to compile |
MacOS 15.1.1 (24B91), Go 1.22.7 (was not able to get CI to match Go 1.22.10 either). |
I've figured out the issue: it was indeed a problem with "untracked changes to any go.mod files in your local copy", specifically whether |
Reverts #37142 as something with this change is not working as expected. Reverting for now to unblock PRs.
See #37170 and #37172