Skip to content
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: jobs/mixed-versions failed #141775

Closed
cockroach-teamcity opened this issue Feb 20, 2025 · 2 comments
Closed

roachtest: jobs/mixed-versions failed #141775

cockroach-teamcity opened this issue Feb 20, 2025 · 2 comments

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented Feb 20, 2025

Note: This build has runtime assertions enabled. If the same failure was hit in a run without assertions enabled, there should be a similar failure without this message. If there isn't one, then this failure is likely due to an assertion violation or (assertion) timeout.

roachtest.jobs/mixed-versions failed with artifacts on release-25.1 @ 044d3302aef60e0469ebbf610aed0cc02122bac8:

(mixedversion.go:800).Run: mixed-version test failure while running step 19 (wait for all nodes (:1-3) to acknowledge cluster version <current> on system tenant): timed out after 10m0s: expected n1 to be at cluster version 25.1, but is still at 24.3-upgrading-to-25.1-step-016: not upgraded yet
test artifacts and logs in: /artifacts/jobs/mixed-versions/run_1

Parameters:

  • arch=amd64
  • cloud=gce
  • coverageBuild=false
  • cpu=4
  • encrypted=false
  • fs=ext4
  • localSSD=true
  • mvtDeploymentMode=system-only
  • mvtVersions=v24.3.6 → release-25.1
  • runtimeAssertionsBuild=true
  • ssd=0
Help

See: roachtest README

See: How To Investigate (internal)

See: Grafana

/cc @cockroachdb/disaster-recovery

This test on roachdash | Improve this report!

Jira issue: CRDB-47997

@cockroach-teamcity cockroach-teamcity added B-runtime-assertions-enabled branch-release-25.1 C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. T-disaster-recovery labels Feb 20, 2025
@msbutler
Copy link
Collaborator

I forgot to bump the upgrade timeout on this test. Sending out a patch shortly.

@msbutler msbutler removed the release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. label Feb 20, 2025
@msbutler msbutler self-assigned this Feb 20, 2025
@msbutler
Copy link
Collaborator

actually, the jobs patch never merged to release-25.1 #141460

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants