-
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
ccl/backupccl: TestBackupAndRestoreJobDescription failed #102519
Comments
flake in logging, unrelated to backup/restore, already tracked in #102588 |
Expiration-based leases don't usually work great with |
Unfortunately basically all of DR's tests start a test server or test cluster and execute backup and restore statements against it, so almost all of our tests are also testing the kvserver, the sql server, and any and all metamorphic behaviors in them, so if we need to skip tests that include running any kvserver metamorphic behaviors under deadlock, then we basically need to skip all of backupccl/*, not just this test, under deadlock? |
put another way: if |
Yeah. I'm thinking about maybe disabling It's a bit unfortunate to lose that combination, but I think we exercise expiration leases enough under deadlock even in non-metamorphic tests. Longer-term, maybe disabling |
102591: kvserver: disable `kv.expiration_leases_only.enabled` metamorphism under deadlock r=erikgrinaker a=erikgrinaker TestClusters are usually so slow under deadlock detection that they're unable to maintain leases/leadership/liveness, especially with expiration leases. Resolves #101612. Resolves #101613. Resolves #101625. Resolves #101626. Resolves #102519. Epic: none Release note: None Co-authored-by: Erik Grinaker <[email protected]>
ccl/backupccl.TestBackupAndRestoreJobDescription failed with artifacts on master @ 3b1bc872bb4bf8e5eb2ad8790ba8ec781167dd1f:
Fatal error:
Stack:
Log preceding fatal error
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-27486
The text was updated successfully, but these errors were encountered: