-
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
pkg/upgrade/upgrademanager/upgrademanager_test: TestPrecondition failed #139562
Comments
Cluster is up around
The attempted
The injected precondition error is 5 minutes later,
Eventually the test times out... lots of other indicators in the log that this is likely a flake due to resource contention. |
140024: upgrademanager: skip TestPrecondition under stress r=srosenberg a=rail Fixes: #139562 Epic: none Release note: None Co-authored-by: Rail Aliiev <[email protected]>
Based on the specified backports for linked PR #140024, I applied the following new label(s) to this issue: branch-release-23.1, branch-release-23.2, branch-release-24.2, branch-release-24.3, branch-release-25.1. Please adjust the labels as needed to match the branches actually affected by this issue, including adding any known older branches. 🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf. |
Fixes: #139562 Epic: none Release note: None
Fixes: #139562 Epic: none Release note: None
Fixes: #139562 Epic: none Release note: None
Fixes: #139562 Epic: none Release note: None
Fixes: #139562 Epic: none Release note: None
Fixes: #139562 Epic: none Release note: None
Fixes: #139562 Epic: none Release note: None
Fixes: #139562 Epic: none Release note: None
Fixes: #139562 Epic: none Release note: None
Fixes: #139562 Epic: none Release note: None
Fixes: #139562 Epic: none Release note: None
pkg/upgrade/upgrademanager/upgrademanager_test.TestPrecondition failed on release-24.1 @ a4743bb42931fb7b9652f4f01bb3a93d7c8ff018:
Parameters:
attempt=1
race=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-46718
The text was updated successfully, but these errors were encountered: