-
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: unskip cdc/crdb-chaos #54201
Conversation
I'm unsure if I should close #37716 right now with this PR since it has some discussion that might be helpful in case the test fails again. I'll close it if we don't see the issue pop up again in the next few days. |
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.
I'm pretty scared about those 15 minutes, so if you ever find yourself with time on your hands there's probably something there.
Reviewable status: complete! 1 of 0 LGTMs obtained (waiting on @andreimatei and @nvanbenschoten)
e50213a
to
ce48e9e
Compare
I ran this test a total of 15 times in parallel and wasn't able to reproduce. Since its been skipped for 2+ releases, it's hard to know what fixed it, but a good guess is cockroachdb#48561. Release note: None Fixes cockroachdb#37716 Release justification: testing only
ce48e9e
to
51d31c1
Compare
I ran 4 instances of this with the target latency set to 5 minutes and they all passed just fine. So I've reduced this target in this PR. We'll see if this pops up again in CI. |
(Bump) |
bors r+ |
Build succeeded: |
I ran this test a total of 15 times in parallel and wasn't able to
reproduce. Since its been skipped for 2+ releases, it's hard to know
what fixed it, but a good guess is #48561.
Release note: None
Fixes #37716
Informs #36879
Release justification: testing only