-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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/kvnemesis: TestKVNemesisMultiNode failed #61322
Comments
(kv/kvnemesis).TestKVNemesisMultiNode failed on master@6de4313ec216161c79fe725fcc31fc87ef1804ea:
MoreParameters:
See this test on roachdash |
(kv/kvnemesis).TestKVNemesisMultiNode failed on master@37cdf01299861235888af3411e699480f5a2d670:
MoreParameters:
See this test on roachdash |
(kv/kvnemesis).TestKVNemesisMultiNode failed on master@b703e663da8ededaee2e28fc39a24e3880ae54cf:
MoreParameters:
See this test on roachdash |
(kv/kvnemesis).TestKVNemesisMultiNode failed on master@a69e6549a71f5a0e83eb13509001f4d7351050fb:
MoreParameters:
See this test on roachdash |
(kv/kvnemesis).TestKVNemesisMultiNode failed on master@93c38e97ddb9d18721eed850180c103fe3c45547:
MoreParameters:
See this test on roachdash |
(kv/kvnemesis).TestKVNemesisMultiNode failed on master@fc68d927f946103a757888fcbd3ac20904c57a6b:
MoreParameters:
See this test on roachdash |
(kv/kvnemesis).TestKVNemesisMultiNode failed on master@bdff5338ca725bf1cfddf7e3f648bbf02ab42999:
MoreParameters:
See this test on roachdash |
(kv/kvnemesis).TestKVNemesisMultiNode failed on master@f3c8f6ed74494f93bd1eb01b1d7569127f127906:
MoreParameters:
See this test on roachdash |
(kv/kvnemesis).TestKVNemesisMultiNode failed on master@3d19b2cf6b290a152b23722fc32e995eed3b437b:
MoreParameters:
See this test on roachdash |
(kv/kvnemesis).TestKVNemesisMultiNode failed on master@893643b63ea0b1cfa4888c6b73b5c68a9c100c3a:
MoreParameters:
See this test on roachdash |
(kv/kvnemesis).TestKVNemesisMultiNode failed on master@3f9f18ebf27dc0fdbf7fa0fce639be1513c12623:
MoreParameters:
See this test on roachdash |
(kv/kvnemesis).TestKVNemesisMultiNode failed on master@d891594d3c998f153b88f631e3c89ac7d12c2a6e:
MoreParameters:
See this test on roachdash |
(kv/kvnemesis).TestKVNemesisMultiNode failed on master@9891b8db5ea2e9339a04fd2731a16658103e969f:
MoreParameters:
See this test on roachdash |
(kv/kvnemesis).TestKVNemesisMultiNode failed on master@df07592e26735be7362ef2b815ee163ead00739e:
MoreParameters:
See this test on roachdash |
(kv/kvnemesis).TestKVNemesisMultiNode failed on master@651184b3cfbd7c6d336bb49e7152e3d48ea06416:
MoreParameters:
See this test on roachdash |
kv/kvnemesis.TestKVNemesisMultiNode failed with artifacts on master @ 2c50690c86b0de434946bb74f0e63aea1907ea20:
Reproduce
To reproduce, try: make stressrace TESTS=TestKVNemesisMultiNode PKG=./pkg/kv/kvnemesis TESTTIMEOUT=5m STRESSFLAGS='-timeout 5m' 2>&1 Parameters in this failure:
|
62580: kv: deflake multi-node kvnemesis r=nvanbenschoten a=nvanbenschoten Fixes #61322. Prep to address #59062. #### kv: don't consider Subsume error as assertion failures These were added in b15e3dd, but that was incorrect. It is valid for a merge that races with another merge or split to hit these case, as the Subsume request is non-transactional. Also, allow `RHS range bounds do not match` errors in kvnemesis. This is a valid error for the reasons mentioned above. #### kv: mark error from Replica.GetSnapshot with errMarkSnapshotError Without it, we see the following errors in kvnemesis: ``` Wraps: (2) error applying x.AdminChangeReplicas(ctx, /Table/50/"244956da", [{ADD_VOTER n2,s2}]) // [n1,s1,r36/1:/Table/{40-50/"ba86b…}]: failed to generate LEARNER_INITIAL snapshot: couldn't find range descriptor ``` #### kv: allow two more errors with TransferLeaseOperation This deflakes TestKVNemesisMultiNode. The test had recently gotten flakier, which I bisected back to 3fe1992. It appears that the changes in that commit made it more likely to hit this `replica not found in RangeDescriptor`, which is returned after a TransferLease request has acquired latches, in addition to the existing `unable to find store \d+ in range` error, which is returned before a TransferLease request has acquired latches. Co-authored-by: Nathan VanBenschoten <[email protected]>
Fixes cockroachdb#61322. This deflakes TestKVNemesisMultiNode. The test had recently gotten more flaky, which I bisected back to 3fe1992. It appears that the changes in that commit made it more likely to hit this `replica not found in RangeDescriptor`, which is returned after a TransferLease request has acquired latches, in addition to the existing `unable to find store \d+ in range` error, which is returned before a TransferLease request has acquired latches.
(kv/kvnemesis).TestKVNemesisMultiNode failed on master@1b18fc1fa8d9194d5e7f9aaa857425d80f0e4970:
More
Parameters:
See this test on roachdash
powered by pkg/cmd/internal/issues
The text was updated successfully, but these errors were encountered: