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/mixed-version failed #99773

Closed
cockroach-teamcity opened this issue Mar 28, 2023 · 3 comments
Closed

roachtest: backup/mixed-version failed #99773

cockroach-teamcity opened this issue Mar 28, 2023 · 3 comments
Assignees
Labels
branch-release-23.1 Used to mark GA and release blockers, technical advisories, and bugs for 23.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
Milestone

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented Mar 28, 2023

roachtest.backup/mixed-version failed with artifacts on release-23.1 @ 3551dc089ac3efcb3772df2109164dcb01e79d8f:

test artifacts and logs in: /artifacts/backup/mixed-version/run_1
(mixedversion.go:366).Run: mixed-version test failure while running step 24 (run "plan and run backups"): waiting for job to finish: job 851694539533189124: current status "running", waiting for "succeeded"

Parameters: ROACHTEST_cloud=gce , ROACHTEST_cpu=4 , ROACHTEST_encrypted=true , ROACHTEST_ssd=0

Help

See: roachtest README

See: How To Investigate (internal)

Same failure on other branches

/cc @cockroachdb/disaster-recovery

This test on roachdash | Improve this report!

Jira issue: CRDB-26069

@cockroach-teamcity cockroach-teamcity added branch-release-23.1 Used to mark GA and release blockers, technical advisories, and bugs for 23.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. labels Mar 28, 2023
@cockroach-teamcity cockroach-teamcity added this to the 23.1 milestone Mar 28, 2023
@renatolabs renatolabs added release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. and removed release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. labels Mar 29, 2023
@renatolabs
Copy link
Contributor

jobs/adopt.go:472 ⋮ [T1,n1] 892  job 851694539533189124: adoption completed with error job 851694539533189124: could not mark as reverting: job 851694539533189124: ‹›
jobs/adopt.go:472 ⋮ [T1,n1] 892 +‹WITH›
jobs/adopt.go:472 ⋮ [T1,n1] 892 +‹	latestpayload AS (SELECT job_id, value FROM system.job_info AS payload WHERE info_key = 'legacy_payload'::BYTES),›
jobs/adopt.go:472 ⋮ [T1,n1] 892 +‹	latestprogress AS (SELECT job_id, value FROM system.job_info AS progress WHERE info_key = 'legacy_progress'::BYTES)›
jobs/adopt.go:472 ⋮ [T1,n1] 892 +‹	SELECT›
jobs/adopt.go:472 ⋮ [T1,n1] 892 +‹		status, payload.value AS payload, progress.value AS progress, claim_session_id, COALESCE(last_run, created), COALESCE(num_runs, 0)›
jobs/adopt.go:472 ⋮ [T1,n1] 892 +‹	FROM system.jobs AS j›
jobs/adopt.go:472 ⋮ [T1,n1] 892 +‹	INNER JOIN latestpayload AS payload ON j.id = payload.job_id›
jobs/adopt.go:472 ⋮ [T1,n1] 892 +‹	LEFT JOIN latestprogress AS progress ON j.id = progress.job_id›
jobs/adopt.go:472 ⋮ [T1,n1] 892 +‹	WHERE id = $1›
jobs/adopt.go:472 ⋮ [T1,n1] 892 +‹: unexpected multiple results›

Should eventually be fixed when #99659 is backported.

@cockroach-teamcity
Copy link
Member Author

roachtest.backup/mixed-version failed with artifacts on release-23.1 @ 7e72aae900c3ff4b44f1643c2d7ba55fbb2cbe23:

test artifacts and logs in: /artifacts/backup/mixed-version/run_1
(mixedversion.go:366).Run: mixed-version test failure while running step 24 (run "plan and run backups"): waiting for job to finish: job 852546723869687811: current status "running", waiting for "succeeded"

Parameters: ROACHTEST_cloud=gce , ROACHTEST_cpu=4 , ROACHTEST_encrypted=true , ROACHTEST_ssd=0

Help

See: roachtest README

See: How To Investigate (internal)

Same failure on other branches

This test on roachdash | Improve this report!

@adityamaru
Copy link
Contributor

Should be fixed as the linked backport is merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch-release-23.1 Used to mark GA and release blockers, technical advisories, and bugs for 23.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
Projects
No open projects
Archived in project
Development

No branches or pull requests

3 participants