Open
Description
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.backup-restore/mixed-version failed with artifacts on master @ 1e0ccb161abf9ae2b349029effd8614ccc337b4a:
(mixedversion.go:851).Run: mixed-version test failure while running step 11 (run "maybe set custom cluster settings"): pq: setting updated but timed out waiting to read new value
test artifacts and logs in: /artifacts/backup-restore/mixed-version/run_1
Parameters:
arch=amd64cloud=gcecoverageBuild=falsecpu=4encrypted=falsefs=ext4localSSD=truemvtDeploymentMode=separate-processmvtVersions=v25.1.5 → masterruntimeAssertionsBuild=truessd=0
Same failure on other branches
- roachtest: backup-restore/mixed-version failed #143650 roachtest: backup-restore/mixed-version failed [A-disaster-recovery B-runtime-assertions-enabled C-test-failure O-roachtest O-robot P-2 T-disaster-recovery branch-release-25.1]
- roachtest: backup-restore/mixed-version failed #143131 roachtest: backup-restore/mixed-version failed [A-disaster-recovery B-runtime-assertions-enabled C-test-failure O-roachtest O-robot P-2 T-disaster-recovery branch-release-24.3.9-rc release-blocker]
- roachtest: backup-restore/mixed-version failed #125677 roachtest: backup-restore/mixed-version failed [C-test-failure O-roachtest O-robot P-3 T-disaster-recovery branch-release-23.1]
This test on roachdash | Improve this report!
Jira issue: CRDB-51129