-
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
upgrade/upgrades: TestBackfillJobsInfoTable failed #103046
Comments
upgrade/upgrades.TestBackfillJobsInfoTable failed with artifacts on release-23.1 @ 43347361e631585acba789669c886d5343276ac0:
Parameters: Same failure on other branches
|
upgrade/upgrades.TestBackfillJobsInfoTable failed with artifacts on release-23.1 @ 6cf937278a19b59b50abdf78f0e257807367600d:
Parameters: Same failure on other branches
|
upgrade/upgrades.TestBackfillJobsInfoTable failed with artifacts on release-23.1 @ f50bdad0bccba79b5017cec446849b9831085457:
Parameters: Same failure on other branches
|
upgrade/upgrades.TestBackfillJobsInfoTable failed with artifacts on release-23.1 @ 029955855b3243eecfbb7fcc0507ec663f7ddf6f:
Parameters: Same failure on other branches
|
upgrade/upgrades.TestBackfillJobsInfoTable failed with artifacts on release-23.1 @ 8cfaf3b4731273cedaa9e81600a7b1778700b702:
Parameters: Same failure on other branches
|
upgrade/upgrades.TestBackfillJobsInfoTable failed with artifacts on release-23.1 @ 7cf4908e4d88fa1cc4127bbc4c4e327e2aed8b6d:
Parameters: Same failure on other branches
|
104821: upgrade: checkpoint fence version for multi-tenant clusters r=JeffSwenson a=JeffSwenson Previously, the tenant upgrade interlock checkpointed the version attached to the upgrade, when it should have checkpointed the fence version. This made it possible for an upgrade to skip versions. The conditions needed for this are rare, but could be triggered by crashes in the upgrade system or by the autoscaler downscaling a serverless cluster with multiple nodes. Release Note: None Fixes: #104884 104876: logic: keep cockroach-go logs in case of failure r=rafiss a=renatolabs This commit makes use of the new `CockroachLogsDirOpt` option introduced in [1] to pass a custom directory where cockroach logs will be stored. This directory is relative to TMPDIR, which is part of the artifacts path when the test runs in CI. With this change, when a logic test using the cockroach-go config fails, we'll be able to see both the test logs as well as the cockroach logs themselves. The latter will be in the `cockroach.stderr` file. [1] cockroachdb/cockroach-go#170 Epic: none Release note: None 104879: upgrades: deflake TestBackfillJobsInfoTable r=stevendanna a=adityamaru Previously, this test created jobs that could be adopted during test execution causing the number of payload/progress updates to be variable. With this change we create startable jobs so that they are not adopted and the number of payload/progress remain constant. Fixes: #103046 Release note: None Co-authored-by: Jeff <[email protected]> Co-authored-by: Renato Costa <[email protected]> Co-authored-by: adityamaru <[email protected]>
Previously, this test created jobs that could be adopted during test execution causing the number of payload/progress updates to be variable. With this change we create startable jobs so that they are not adopted and the number of payload/progress remain constant. Fixes: cockroachdb#103046 Release note: None
upgrade/upgrades.TestBackfillJobsInfoTable failed with artifacts on release-23.1 @ a0a3b078882aa1f1a73f6683fd5fef0137626fed:
Parameters:
TAGS=bazel,gss,deadlock
Help
See also: How To Investigate a Go Test Failure (internal)
Same failure on other branches
This test on roachdash | Improve this report!
Jira issue: CRDB-27810
The text was updated successfully, but these errors were encountered: