-
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/kvserver: TestStoreRangeSplitRaceUninitializedRHS failed [skipped] #98840
Comments
cc @cockroachdb/replication |
I recently re enabled this test xref #66480. I didn't stress or stress race under a deadlock build which could be why it didnt flake over a few k runs. I also don't have a good feel for whether this test is still valuable +@erikgrinaker . |
We'll have a look, thanks. |
kv/kvserver.TestStoreRangeSplitRaceUninitializedRHS failed with artifacts on master @ 0a72a49eb6e4ce5823b53d02125441c3da2e94f5:
Parameters: |
kv/kvserver.TestStoreRangeSplitRaceUninitializedRHS failed with artifacts on master @ 53dbb86acb1d48309530181b94838faf937084d3:
Parameters: |
kv/kvserver.TestStoreRangeSplitRaceUninitializedRHS failed with artifacts on master @ 53dbb86acb1d48309530181b94838faf937084d3:
Parameters: |
I'm going to re-open this to track the skipped test. |
cc @cockroachdb/replication |
It's still running, just not under deadlock/race. We have lots of these integration tests that have implicit timing dependencies because we're spinning up actual in-memory clusters, and some of them just don't work at all under deadlock/race because these are too slow, and they never will. |
Ah cool. Thanks for the context. |
kv/kvserver.TestStoreRangeSplitRaceUninitializedRHS failed with artifacts on master @ 11fbbca584e3bd774ebee3ee94c49ca30a096b26:
Parameters:
TAGS=bazel,gss,deadlock
Help
See also: How To Investigate a Go Test Failure (internal)
This test on roachdash | Improve this report!
Jira issue: CRDB-25542
The text was updated successfully, but these errors were encountered: