-
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
roachtest: backup-restore/online-restore failed [relation "[239]" does not exist during schemachange workload] #129187
Labels
branch-release-24.2
Used to mark GA and release blockers, technical advisories, and bugs for 24.2
C-test-failure
Broken test (automatically or manually discovered).
O-roachtest
O-robot
Originated from a bot.
P-2
Issues/test failures with a fix SLA of 3 months
T-sql-foundations
SQL Foundations Team (formerly SQL Schema + SQL Sessions)
Comments
cockroach-teamcity
added
branch-release-24.2
Used to mark GA and release blockers, technical advisories, and bugs for 24.2
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
Aug 18, 2024
stevendanna
added
P-2
Issues/test failures with a fix SLA of 3 months
and removed
release-blocker
Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked.
labels
Aug 23, 2024
schema change workload failure. routing to foundations in case this is new:
|
msbutler
added
T-sql-foundations
SQL Foundations Team (formerly SQL Schema + SQL Sessions)
and removed
T-disaster-recovery
labels
Aug 27, 2024
rafiss
changed the title
roachtest: backup-restore/online-restore failed
roachtest: backup-restore/online-restore failed [relation "[239]" does not exist]
Aug 30, 2024
rafiss
changed the title
roachtest: backup-restore/online-restore failed [relation "[239]" does not exist]
roachtest: backup-restore/online-restore failed [relation "[239]" does not exist during schemachange workload]
Aug 30, 2024
I wonder if this is similar to: #129857, let see if fixing that one sorts this out |
annrpom
added a commit
to annrpom/cockroach
that referenced
this issue
Sep 9, 2024
This patch enables `ALTER TABLE ... ALTER PRIMARY KEY` in the schemachange workload. Fixes: cockroachdb#129187 Release note: None
annrpom
added a commit
to annrpom/cockroach
that referenced
this issue
Sep 9, 2024
This patch enables `ALTER TABLE ... ALTER PRIMARY KEY` in the schemachange workload. Fixes: cockroachdb#129187 Release note: None
This was referenced Sep 16, 2024
Closing since error hasn't occurred recently; missing logs as well |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
branch-release-24.2
Used to mark GA and release blockers, technical advisories, and bugs for 24.2
C-test-failure
Broken test (automatically or manually discovered).
O-roachtest
O-robot
Originated from a bot.
P-2
Issues/test failures with a fix SLA of 3 months
T-sql-foundations
SQL Foundations Team (formerly SQL Schema + SQL Sessions)
roachtest.backup-restore/online-restore failed with artifacts on release-24.2 @ ad78dc73db84c9749fd5d8da982bab8030376251:
Parameters:
ROACHTEST_arch=amd64
ROACHTEST_cloud=gce
ROACHTEST_coverageBuild=false
ROACHTEST_cpu=4
ROACHTEST_encrypted=false
ROACHTEST_fs=ext4
ROACHTEST_localSSD=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!
Jira issue: CRDB-41426
The text was updated successfully, but these errors were encountered: