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/round-trip failed #124333

Closed
cockroach-teamcity opened this issue May 17, 2024 · 3 comments
Closed

roachtest: backup-restore/round-trip failed #124333

cockroach-teamcity opened this issue May 17, 2024 · 3 comments
Assignees
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. T-disaster-recovery

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented May 17, 2024

roachtest.backup-restore/round-trip failed with artifacts on master @ 855b9cc97afa3df4f7e17f928c04ab0834b2630c:

(monitor.go:154).Wait: monitor failure: full command output in run_062304.884571858_n4_COCKROACHRANDOMSEED7.log: COMMAND_PROBLEM: exit status 1
test artifacts and logs in: /artifacts/backup-restore/round-trip/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

/cc @cockroachdb/disaster-recovery

This test on roachdash | Improve this report!

Jira issue: CRDB-38831

@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 17, 2024
@msbutler msbutler self-assigned this May 17, 2024
@msbutler msbutler removed the release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. label May 17, 2024
@msbutler
Copy link
Collaborator

this looks like a test infra bug: the systemTableWriter may add comments to any table in any db, including tables in the schema change db. But i don't think the schema change workload expects anyone else is manipulating objects in its database. we should prevent the systemTableWriter from operating on the schemachange db.

@msbutler
Copy link
Collaborator

observed this log line:

07:00:58 mixed_version_backup.go:1257: removing comment from table: schemachange.seq_w4_193
07:00:58 mixed_version_backup.go:1329: error running operation: pq: relation "schemachange.seq_w4_193" does not exist

@msbutler
Copy link
Collaborator

hasn't flaked in 2 weeks. 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. T-disaster-recovery
Development

No branches or pull requests

2 participants