-
-
Notifications
You must be signed in to change notification settings - Fork 614
CA: Run all table test subtests in parallel #7452
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
Conversation
Given go1.22's change to how loopvars work, this rebinding shouldn't be necessary. These loops should Just Work (tm) and be able to run in parallel anyway. |
I would love for that to be the case, but I receive warnings like the one reported here. Edit: This report is more apt golang/go#66876 |
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.
Ah, good find. So the rebindings are necessary not to appease the Go compiler, but to appease a bug in gopls. In that case, this LGTM, but let's file a bug to remove all foo := foo
rebindings once gopls gets an update to fix the bug.
[Previously](letsencrypt#7438) I had made a change to run all CA tests in parallel, which was great, but I failed to account for several table driven tests. By rebinding the subtest's iterator to the lexical scope, each subtest can now run in parallel.
[Previously](letsencrypt#7438) I had made a change to run all CA tests in parallel, which was great, but I failed to account for several table driven tests. By rebinding the subtest's iterator to the lexical scope, each subtest can now run in parallel.
Previously I had made a change to run all CA tests in parallel, which was great, but I failed to account for several table driven tests. By rebinding the subtest's iterator to the lexical scope, each subtest can now run in parallel.