-
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
kv/kvserver: TestDecommission failed #79879
Comments
Adding GA-blocker cc @cockroachdb/storage |
This error almost always indicates something above Pebble is failing to close an Iterator. |
Unfortunately, this didn't seem trivially reproducible - I ran for ~2 hours on my gceworker with the following, at the same SHA this test failed at, and didn't get any hits: $ bazel test pkg/kv/kvserver:all \
--test_env=GOTRACEBACK=all \
--test_filter=TestDecommission$ \
--test_sharding_strategy=disabled \
--test_output errors \
--run_under '@com_github_cockroachdb_stress//:stress -maxruns 1000 -maxtime 1h0m0s -maxfails 1 -p 4' \
--define gotags=bazel,gss \
--nocache_test_results \
--test_output streamed I think cockroachdb/pebble#1597 will help with debugging this type of issue eventually, though it's basically a thought experiment at this point. |
kv/kvserver.TestDecommission failed with artifacts on master @ 0add8527e82d0ae4987ea7105778c7aa6e43bd3a:
Help
See also: How To Investigate a Go Test Failure (internal)
|
Above was same failure mode:
|
We have marked this test failure issue as stale because it has been |
kv/kvserver.TestDecommission failed with artifacts on master @ 3aa37f1c499f7c73dd3fa178cc5e2687e9e23311:
Help
See also: How To Investigate a Go Test Failure (internal)
Parameters in this failure:
This test on roachdash | Improve this report!
Jira issue: CRDB-15881
The text was updated successfully, but these errors were encountered: