-
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/kvclient/kvcoord: TestTransactionUnexpectedlyCommitted failed #110187
Comments
kv/kvclient/kvcoord.TestTransactionUnexpectedlyCommitted failed with artifacts on master @ 9d3115d1030ee7526818768913285dd0426dd9b5:
Parameters: |
FYI: Test also failed under remote execution: https://tanzanite.cluster.engflow.com/invocation/bd7b98ed-b76c-4ce7-b4bf-213a108482a1#targets-Ly9wa2cva3Yva3ZjbGllbnQva3Zjb29yZDprdmNvb3JkX3Rlc3Q=, run 19 (shard 6) |
kv/kvclient/kvcoord.TestTransactionUnexpectedlyCommitted failed with artifacts on master @ 28552c8876e8d6764c2102effbb8d9842185123d:
Parameters: |
kv/kvclient/kvcoord.TestTransactionUnexpectedlyCommitted failed with artifacts on master @ 49eef749235f15d57153cb00f48dfd3b27be6c54:
Parameters: |
kv/kvclient/kvcoord.TestTransactionUnexpectedlyCommitted failed with artifacts on master @ b1a641f1d27653a4e93154926be57d0cae864bd6:
Parameters: |
Flaky test. Informs cockroachdb#110187 Release note: None
111205: kvcoord: skip TestTransactionUnexpectedlyCommitted r=nvanbenschoten a=arulajmani Flaky test. Informs #110187 Release note: None Co-authored-by: Arul Ajmani <[email protected]>
The `TestTransactionUnexpectedlyCommitted/recovery_after_transfer_lease` test, introduced to test cockroachdb#107658, has been flaky (particularly under deadlock builds) due to a race condition between a retry of a write and intent resolution. While both orderings in this test result in a correct `AmbiguousResultError` for the client, when intent resolution wins the race, the retried write will attempt to push away the current lockholder; since it is illegal for a committed transaction to perform a push, this results in a different secondary error attached to the `AmbiguousResultError`. This change ensures a predefined ordering of these operations so that the secondary error is consistent across runs of the test. Fixes: cockroachdb#110187 Release note: None
109781: spanconfig: pass SpanConfig by pointer r=arulajmani a=andrewbaptist Note: Only the last 2 commits are only in this PR. SpanConfig can be a large object and it is more efficient to pass by pointer now that it goes through multiple layers of code. Epic: none Release note: None 111090: kvcoord: fix flake in `TestTransactionUnexpectedlyCommitted` r=AlexTalks a=AlexTalks The `TestTransactionUnexpectedlyCommitted/recovery_after_transfer_lease` test, introduced to test #107658, has been flaky (particularly under deadlock builds) due to a race condition between a retry of a write and intent resolution. While both orderings in this test result in a correct `AmbiguousResultError` for the client, when intent resolution wins the race, the retried write will attempt to push away the current lockholder; since it is illegal for a committed transaction to perform a push, this results in a different secondary error attached to the `AmbiguousResultError`. This change ensures a predefined ordering of these operations so that the secondary error is consistent across runs of the test. Fixes: #110187 Release note: None 111369: clusterversion: fix formatting of versions comment r=RaduBerinde a=RaduBerinde Some of the formatting in this big comment is getting screwed up by gofmt. This change fixes it - the trick was to make sure the "sub lists" are all indented by a tab so it's all treated like a big code block. Epic: none Release note: None 111372: roachtest: fix leaked goroutines in c2c roachtests r=lidorcarmel a=lidorcarmel Without this PR, c2c roachtests have almost 30 messages like these at the end: ``` 18:04:19 leaktest.go:161: Leaked goroutine: goroutine 1879 [select, 2 minutes]: database/sql.(*DB).connectionOpener(0xc003f2bc70, {0x10812e000, 0xc00059d220}) GOROOT/src/database/sql/sql.go:1218 +0x8d created by database/sql.OpenDB GOROOT/src/database/sql/sql.go:791 +0x18d ``` This PR cleans that up. Epic: none Release note: None Co-authored-by: Andrew Baptist <[email protected]> Co-authored-by: Alex Sarkesian <[email protected]> Co-authored-by: Radu Berinde <[email protected]> Co-authored-by: Lidor Carmel <[email protected]>
The `TestTransactionUnexpectedlyCommitted/recovery_after_transfer_lease` test, introduced to test cockroachdb#107658, has been flaky (particularly under deadlock builds) due to a race condition between a retry of a write and intent resolution. While both orderings in this test result in a correct `AmbiguousResultError` for the client, when intent resolution wins the race, the retried write will attempt to push away the current lockholder; since it is illegal for a committed transaction to perform a push, this results in a different secondary error attached to the `AmbiguousResultError`. This change ensures a predefined ordering of these operations so that the secondary error is consistent across runs of the test. Fixes: cockroachdb#110187 Release note: None
The `TestTransactionUnexpectedlyCommitted/recovery_after_transfer_lease` test, introduced to test cockroachdb#107658, has been flaky (particularly under deadlock builds) due to a race condition between a retry of a write and intent resolution. While both orderings in this test result in a correct `AmbiguousResultError` for the client, when intent resolution wins the race, the retried write will attempt to push away the current lockholder; since it is illegal for a committed transaction to perform a push, this results in a different secondary error attached to the `AmbiguousResultError`. This change ensures a predefined ordering of these operations so that the secondary error is consistent across runs of the test. Fixes: cockroachdb#110187 Release note: None
The `TestTransactionUnexpectedlyCommitted/recovery_after_transfer_lease` test, introduced to test cockroachdb#107658, has been flaky (particularly under deadlock builds) due to a race condition between a retry of a write and intent resolution. While both orderings in this test result in a correct `AmbiguousResultError` for the client, when intent resolution wins the race, the retried write will attempt to push away the current lockholder; since it is illegal for a committed transaction to perform a push, this results in a different secondary error attached to the `AmbiguousResultError`. This change ensures a predefined ordering of these operations so that the secondary error is consistent across runs of the test. Fixes: cockroachdb#110187 Release note: None
kv/kvclient/kvcoord.TestTransactionUnexpectedlyCommitted failed with artifacts on master @ cd2e06079050eb1d9df004ea2e2d22ce03dd3b3a:
Help
See also: How To Investigate a Go Test Failure (internal)
This test on roachdash | Improve this report!
Jira issue: CRDB-31311
The text was updated successfully, but these errors were encountered: