Closed cockroach-teamcity closed 1 month ago
This doesn't appear to be a release blocker. The test assumes that there will be at least 3 scan requests for the range because there are 4 ranges (0-250, 250-500, 500-750 and 750+) - in the test it ends up doing a single scan which covers all 4 ranges.
This doesn't seem like incorrect behavior, but it is unexpected since we had 4 ranges and 3 workers, so it is inefficient. I will spend some time later this week to try and bisect to see if anything that changed recently made this more flakey.
This has happened before and an attempt to fix it was done in https://github.com/cockroachdb/cockroach/pull/118881, but this seems insufficient still. This is a rare flake, but should be addressed eventually.
We have marked this test failure issue as stale because it has been inactive for 1 month. If this failure is still relevant, removing the stale label or adding a comment will keep it active. Otherwise, we'll close it in 5 days to keep the test failure queue tidy.
kv/kvclient/rangefeed.TestDBClientScan failed with artifacts on release-23.2 @ b5a9e987af5f8b8eabbaa31db2b19ec270099d0f:
Parameters:
TAGS=bazel,gss,deadlock
stress=true
Help
See also: How To Investigate a Go Test Failure (internal)
/cc @cockroachdb/replicationThis test on roachdash | Improve this report!
Jira issue: CRDB-41671