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

ccl/backupccl: TestFullClusterBackup failed #137902

Open
cockroach-teamcity opened this issue Dec 22, 2024 · 0 comments
Open

ccl/backupccl: TestFullClusterBackup failed #137902

cockroach-teamcity opened this issue Dec 22, 2024 · 0 comments
Labels
A-disaster-recovery 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-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

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented Dec 22, 2024

ccl/backupccl.TestFullClusterBackup failed on release-24.2 @ de49acf81407af360cea5a78cf66b808305fcf0d:

Fatal error:

panic: test timed out after 14m57s
running tests:
	TestFullClusterBackup (13m16s)
	TestFullClusterBackup/inSystemTenant=true (15s)

Stack:

goroutine 568037 [running]:
testing.(*M).startAlarm.func1()
	GOROOT/src/testing/testing.go:2366 +0x385
created by time.goFunc
	GOROOT/src/time/sleep.go:177 +0x2d
Log preceding fatal error

=== RUN   TestFullClusterBackup
    test_log_scope.go:165: test logs captured to: outputs.zip/logTestFullClusterBackup2715428574
    test_log_scope.go:76: use -show-logs to present logs inline
=== RUN   TestFullClusterBackup/inSystemTenant=false/zone_configs
=== RUN   TestFullClusterBackup/inSystemTenant=false/ensure_all_databases_restored
=== RUN   TestFullClusterBackup/inSystemTenant=false/ensure_that_tables_can_be_created_at_the_excepted_ID
=== RUN   TestFullClusterBackup/inSystemTenant=false/ensure_user_table_data_restored
=== RUN   TestFullClusterBackup/inSystemTenant=false/ensure_zones_are_restored_during_pre-restore
=== RUN   TestFullClusterBackup/inSystemTenant=false
    testutils.go:296: no Invalid Descriptors
    testutils.go:296: no Invalid Descriptors
=== RUN   TestFullClusterBackup/inSystemTenant=false/ensure_all_schemas_are_restored
=== RUN   TestFullClusterBackup/inSystemTenant=false/ensure_system_table_data_restored
=== RUN   TestFullClusterBackup/inSystemTenant=false/ensure_that_grants_are_restored
=== RUN   TestFullClusterBackup/inSystemTenant=true

Parameters:

  • attempt=1
  • run=9
  • shard=36
Help

See also: How To Investigate a Go Test Failure (internal)

/cc @cockroachdb/disaster-recovery

This test on roachdash | Improve this report!

Jira issue: CRDB-45801

@cockroach-teamcity 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-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 Dec 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-disaster-recovery 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-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
None yet
Development

No branches or pull requests

1 participant