-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
roachtest: attempt to fix cancel test #41032
Conversation
LGTM I wonder how hard it is to write a linter for this... |
bors r+" |
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.
Reviewable status: complete! 0 of 0 LGTMs obtained (waiting on @jordanlewis)
pkg/cmd/roachtest/cancel.go, line 59 at r1 (raw file):
for _, q := range queries { sem := make(chan struct{}, 1) go func(q string) {
i wonder why q
needs to be a param, but t
and queryPrefix
do not?
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.
Reviewable status: complete! 0 of 0 LGTMs obtained (waiting on @rafiss)
pkg/cmd/roachtest/cancel.go, line 59 at r1 (raw file):
Previously, rafiss (Rafi Shamim) wrote…
i wonder why
q
needs to be a param, butt
andqueryPrefix
do not?
only things that are "changing" in the loop need to be captured as arguments
Build failed |
There was some suspicious stuff going on in the test, which has been failing - try to fix it in the hopes that next time it'll be more clear what's going on. Release note: None Release justification: test-only change
68037fe
to
27d2fe4
Compare
Oops, used the wrong logger method... bors r+ |
41032: roachtest: attempt to fix cancel test r=jordanlewis a=jordanlewis There was some suspicious stuff going on in the test, which has been failing - try to fix it in the hopes that next time it'll be more clear what's going on. Attempt to fix #38417 Release note: None Release justification: test-only change Co-authored-by: Jordan Lewis <[email protected]>
Build succeeded |
There was some suspicious stuff going on in the test, which has been
failing - try to fix it in the hopes that next time it'll be more clear
what's going on.
Attempt to fix #38417
Release note: None
Release justification: test-only change