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: backup-restore/mixed-version failed #123620

Closed
cockroach-teamcity opened this issue May 4, 2024 · 5 comments
Closed

roachtest: backup-restore/mixed-version failed #123620

cockroach-teamcity opened this issue May 4, 2024 · 5 comments
Labels
branch-master Failures on the master branch. C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. P-3 Issues/test failures with no fix SLA release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. T-disaster-recovery
Milestone

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented May 4, 2024

roachtest.backup-restore/mixed-version failed with artifacts on master @ 6e23d32dd0d36181f5c886c9a0eda9c756005bd6:

(mixedversion.go:592).Run: mixed-version test failure while running step 28 (run "plan and run backups"): error resuming job 965822453793325060: pq: job 965822453793325060: job with status pause-requested cannot be resumed
test artifacts and logs in: /artifacts/backup-restore/mixed-version/run_1

Parameters:

  • ROACHTEST_arch=amd64
  • ROACHTEST_cloud=gce
  • ROACHTEST_coverageBuild=false
  • ROACHTEST_cpu=4
  • ROACHTEST_encrypted=false
  • ROACHTEST_metamorphicBuild=false
  • ROACHTEST_ssd=0
Help

See: roachtest README

See: How To Investigate (internal)

See: Grafana

Same failure on other branches

/cc @cockroachdb/disaster-recovery

This test on roachdash | Improve this report!

Jira issue: CRDB-38429

@cockroach-teamcity cockroach-teamcity added branch-master Failures on the master branch. 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 May 4, 2024
@cockroach-teamcity cockroach-teamcity added this to the 24.1 milestone May 4, 2024
@cockroach-teamcity
Copy link
Member Author

roachtest.backup-restore/mixed-version failed with artifacts on master @ 6e23d32dd0d36181f5c886c9a0eda9c756005bd6:

(mixedversion.go:592).Run: mixed-version test failure while running step 2 (start cluster at version "v22.1.22"): COMMAND_PROBLEM: exit status 1
test artifacts and logs in: /artifacts/backup-restore/mixed-version/run_1

Parameters:

  • ROACHTEST_arch=amd64
  • ROACHTEST_cloud=gce
  • ROACHTEST_coverageBuild=false
  • ROACHTEST_cpu=4
  • ROACHTEST_encrypted=true
  • ROACHTEST_metamorphicBuild=false
  • ROACHTEST_ssd=0
Help

See: roachtest README

See: How To Investigate (internal)

See: Grafana

Same failure on other branches

This test on roachdash | Improve this report!

@cockroach-teamcity
Copy link
Member Author

roachtest.backup-restore/mixed-version failed with artifacts on master @ 379d332c9a4ce49cda4a3565a852e7ddb850ffb5:

(mixedversion.go:592).Run: mixed-version test failure while running step 2 (start cluster at version "v22.1.22"): COMMAND_PROBLEM: exit status 1
test artifacts and logs in: /artifacts/backup-restore/mixed-version/run_1

Parameters:

  • ROACHTEST_arch=amd64
  • ROACHTEST_cloud=gce
  • ROACHTEST_coverageBuild=false
  • ROACHTEST_cpu=4
  • ROACHTEST_encrypted=false
  • ROACHTEST_metamorphicBuild=false
  • ROACHTEST_ssd=0
Help

See: roachtest README

See: How To Investigate (internal)

See: Grafana

Same failure on other branches

This test on roachdash | Improve this report!

@exalate-issue-sync exalate-issue-sync bot added the P-3 Issues/test failures with no fix SLA label May 6, 2024
@benbardin
Copy link
Collaborator

Suspect test race

@renatolabs
Copy link
Collaborator

renatolabs commented May 6, 2024

Last two failures have been fixed by #123603. First failure is probably because the test should wait before calling RESUME.

@msbutler
Copy link
Collaborator

hasn't flaked in a month. closing.

Disaster Recovery Backlog automation moved this from Backlog to Done May 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch-master Failures on the master branch. C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. P-3 Issues/test failures with no fix SLA release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. T-disaster-recovery
Development

No branches or pull requests

4 participants