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: loqrecovery/half-online/workload=tpcc/rangeSize=16mb failed #97912
Comments
|
@herkolategan in #96949 you added a mandatory consistency check to the end of roachtest. Quorum recovery tests often leave cluster broken if it is impossible to recover all replicas. Any ideas on how to make that check optional if test knows recovery didn't succeed? Unsuccessful recovery is a pass for the test. |
@aliher1911 Thanks for pointing this out! I'll create an issue to add something to be able to opt out of the mandatory consistency check. |
A few post validations are currently performed after a test completes. In most cases it applies to all tests, but there are some tests that are incompatible with particular post validations. This change adds the ability for a test to specify that it wants to opt-out of certain validations. Refs: cockroachdb#97912 Epic: None
A few post validations are currently performed after a test completes. In most cases it applies to all tests, but there are some tests that are incompatible with particular post validations. This change adds the ability for a test to specify that it wants to opt-out of certain validations. Refs: cockroachdb#97912 Epic: None
A few post validations are currently performed after a test completes. In most cases it applies to all tests, but there are some tests that are incompatible with particular post validations. This change adds the ability for a test to specify that it wants to opt-out of certain validations. Refs: cockroachdb#97912 Epic: None
98848: roachtest: allow opting out of post validation(s) r=aliher1911 a=herkolategan A few post validations are currently performed after a test completes. In most cases it applies to all tests, but there are some tests that are incompatible with particular post validations. This change adds the ability for a test to specify that it wants to opt-out of certain validations. Refs: #97912 Epic: None Co-authored-by: Herko Lategan <herko@cockroachlabs.com>
A few post validations are currently performed after a test completes. In most cases it applies to all tests, but there are some tests that are incompatible with particular post validations. This change adds the ability for a test to specify that it wants to opt-out of certain validations. Refs: cockroachdb#97912 Epic: None
roachtest.loqrecovery/half-online/workload=tpcc/rangeSize=16mb failed with artifacts on master @ 0fcc33bc2870961b9387999d8a9fed97fccbb2ae:
Parameters: |
roachtest.loqrecovery/half-online/workload=tpcc/rangeSize=16mb failed with artifacts on master @ d107217dac5d817cc115bc0e97b7e53c0f2878bf:
Parameters: |
Looks like this is a completely new issue with changing range size. |
Yes, see #96725. |
roachtest.loqrecovery/half-online/workload=tpcc/rangeSize=16mb failed with artifacts on master @ 2bd2c806ab3044569b09e0a205b5bc0452ad4e2b:
Parameters: |
roachtest.loqrecovery/half-online/workload=tpcc/rangeSize=16mb failed with artifacts on master @ 143b63a6a27aeb286637dd2e5abddafdf0c51874:
Parameters: |
Subsequent failure is now fixed by #99636. All good. |
roachtest.loqrecovery/half-online/workload=tpcc/rangeSize=16mb failed with artifacts on master @ 20e2adda3c76c7172dd986c871df0ae9a346918f:
Parameters:
ROACHTEST_cloud=gce
,ROACHTEST_cpu=4
,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-24961
The text was updated successfully, but these errors were encountered: