-
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: kv/contention/nodes=4 failed #50864
Comments
(roachtest).kv/contention/nodes=4 failed on master@3e0de239121813ea4d47873388a2828a66d9edf7:
More
Artifacts: /kv/contention/nodes=4
See this test on roachdash |
Hits the 10m timeout with this message repeating: |
Second failure.
Test was happily chugging along before zero-ing out for good. Couldn't fetch logs/debug zip after.
Is this an infra-flake? Saw it happen #50763 (comment). First failure is different, and more interesting. I think this is something real we should look at. Seeing a "clogging" of the txn wait queue:
Elsewhere:
Assigning myself to bring it up tomorrow. |
most recent: #45698 |
(roachtest).kv/contention/nodes=4 failed on master@3a03f3843a8cdf04f82c52753c61cf01b0d2ddcd:
More
Artifacts: /kv/contention/nodes=4
Related:
roachtest: kv/contention/nodes=4 failed #50542 roachtest: kv/contention/nodes=4 failed C-test-failure O-roachtest O-robot branch-provisional_202006230817_v19.2.8 release-blocker
roachtest: kv/contention/nodes=4 failed #48727 roachtest: kv/contention/nodes=4 failed C-test-failure O-roachtest O-robot branch-provisional_202005112258_v19.2.7 release-blocker
roachtest: kv/contention/nodes=4 failed #45698 roachtest: kv/contention/nodes=4 failed C-test-failure O-roachtest O-robot branch-release-19.2 release-blocker
See this test on roachdash
powered by pkg/cmd/internal/issues
The text was updated successfully, but these errors were encountered: