-
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
kv/kvclient/kvcoord: TestMuxRangeFeedDoesNotStallOnError failed #136316
Comments
kv/kvclient/kvcoord.TestMuxRangeFeedDoesNotStallOnError failed on master @ c9257531b739e41eee3d5d57fad6324eaac5d639:
Parameters:
|
kv/kvclient/kvcoord.TestMuxRangeFeedDoesNotStallOnError failed with artifacts on master @ 0f2422bac446d1d297cec730ec7817aef46bd2be:
|
kv/kvclient/kvcoord.TestMuxRangeFeedDoesNotStallOnError failed with artifacts on master @ c9257531b739e41eee3d5d57fad6324eaac5d639:
|
This test was merged a couple of days ago and has been flaky since (#134776). |
Not a release blocker because the test fails during setup. I'll send out a PR to deflake. |
During setup, this test wants to ensure that there's atleast one non-local range to node 1. Previously, we'd only scatter once, which meant if we got unlucky on that scatter, the setup condition could never be satisfied. This patch moves the scatter into the succeeds soon bit where we're checking the non-local range condition. Closes cockroachdb#136316 Release note: None
kv/kvclient/kvcoord.TestMuxRangeFeedDoesNotStallOnError failed on master @ bcc993d796d03664604bf695e38fd5644d0bc952:
Parameters:
|
kv/kvclient/kvcoord.TestMuxRangeFeedDoesNotStallOnError failed with artifacts on master @ fa7b97990f45bdf3d7f7896b66379489934091c8:
Help
See also: How To Investigate a Go Test Failure (internal)
This test on roachdash | Improve this report!
Jira issue: CRDB-44970
The text was updated successfully, but these errors were encountered: