-
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: clearrange/checks=true/rangeTs=true failed #104078
Comments
Looks like a divergence in SysBytes. This is 23.1 so I think the divergence is expected, but I don't think the fataling is, looking at the PR description of #99244.
|
cc @cockroachdb/replication |
This test explicitly enables the fatal assertion:
We've fixed/mitigated these races on These races are also more likely to get tickled by expiration leases, which were metamorphically enabled on master and You can consider disabling the fatal stats assertion on the release branches. |
Previously, the checks=true configuration of the clearrange roachtest would fatal on stats divergences. Due to cockroachdb#93896, this test can fatal with a SysBytes divergence. This is fixed on master, but the fix will not be backported to 23.1 or 22.2. Disable the enforcement of consistent stats on this branch. Fixes cockroachdb#104078. Informs cockroachdb#104011. Epic: none Release note: none Release justification: non-production code changes
Thanks, should've looked at that PR; I didn't realize it was kvnemesis specific. Created #104152. |
roachtest.clearrange/checks=true/rangeTs=true failed with artifacts on release-23.1 @ f462a0e04526d90b004b6865938587a1bec28c21:
Parameters:
ROACHTEST_cloud=gce
,ROACHTEST_cpu=16
,ROACHTEST_encrypted=false
,ROACHTEST_ssd=0
Help
See: roachtest README
See: How To Investigate (internal)
This test on roachdash | Improve this report!
Jira issue: CRDB-28345
The text was updated successfully, but these errors were encountered: