-
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/kvflowcontrol/rac2: TestRangeController failed #132293
Comments
Dup of #132040. |
kv/kvserver/kvflowcontrol/rac2.TestRangeController failed on master @ 645eb8c99796b3b88f5631aa0fc92a011010ce64:
Parameters:
|
kv/kvserver/kvflowcontrol/rac2.TestRangeController failed on master @ 30dbb173d0f083b35cf9eb8093832a5dd764c5af:
Parameters:
|
kv/kvserver/kvflowcontrol/rac2.TestRangeController failed on master @ a0f39e7ac9574756063bc90bba6bc532b45c33d4:
Parameters:
|
kv/kvserver/kvflowcontrol/rac2.TestRangeController failed on master @ a1b013e763abd1454603985996a45663b6e6bcad:
Parameters:
|
132653: rac2: fix mutex ordering issues in tests r=kvoli a=pav-kv The problem is partly described in #132293 (comment), but the same thing applies to the `scheduledMu` mutex. This PR is a minimal fix to get the `--deadlock` CI failures out the way, though this test needs a better refactoring. The purpose/scope of the extra mutexes in the test harness is unclear, and should be revisited and specified. In a deterministic test, there should be no need for extra mutexes - their existence indicates that either the test is non-deterministic, or the mutexes are mostly redundant (and so we should be clear about their purpose). Fixes #132040, #132293 Co-authored-by: Pavel Kalinnikov <pavel@cockroachlabs.com>
kv/kvserver/kvflowcontrol/rac2.TestRangeController failed with artifacts on release-24.3 @ ab649c44652184290d1177e989330339f3d8c9ec:
|
The last failure is different from the one that opened this issue. The initial one is fixed. I put a |
The new failure came up again in #133426. Since the original failure was fixed, closing this issue. |
kv/kvserver/kvflowcontrol/rac2.TestRangeController failed on master @ d063517b3f15b1d0ec43206802acc7e3981e5d5b:
Parameters:
attempt=1
deadlock=true
run=1
shard=1
Help
See also: How To Investigate a Go Test Failure (internal)
This test on roachdash | Improve this report!
Jira issue: CRDB-42929
Epic CRDB-37515
The text was updated successfully, but these errors were encountered: