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: TestBackupCheckpointing failed #142025

Open
cockroach-teamcity opened this issue Feb 26, 2025 · 0 comments
Open

ccl/backupccl: TestBackupCheckpointing failed #142025

cockroach-teamcity opened this issue Feb 26, 2025 · 0 comments
Labels
A-disaster-recovery branch-release-23.2 Used to mark GA and release blockers, technical advisories, and bugs for 23.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
Milestone

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented Feb 26, 2025

ccl/backupccl.TestBackupCheckpointing failed with artifacts on release-23.2 @ d04960338a3f63657cb230891685f758d0d35d87:

Fatal error:

panic: test timed out after 14m55s
running tests:
	TestBackupCheckpointing (14m55s)
	TestBackupCheckpointing/introduce-spans (14m45s)

Stack:

goroutine 788110 [running]:
testing.(*M).startAlarm.func1()
	GOROOT/src/testing/testing.go:2259 +0x3b9
created by time.goFunc
	GOROOT/src/time/sleep.go:176 +0x2d
Log preceding fatal error

=== RUN   TestBackupCheckpointing
    test_log_scope.go:165: test logs captured to: /artifacts/tmp/_tmp/d634ad81c100b2cd21a935f08b59038c/logTestBackupCheckpointing471061083
    test_log_scope.go:76: use -show-logs to present logs inline
=== RUN   TestBackupCheckpointing/full-backup
    test_server_shim.go:154: automatically injected a shared process virtual cluster under test; see comment at top of test_server_shim.go for details.

pkg/ccl/backupccl/backup_test.go:1554: (TestBackupCheckpointing.func5)
	NOTICE: .ExecutorConfig() called via implicit interface ApplicationLayerInterface;
HINT: consider using .ApplicationLayer().ExecutorConfig() instead.
TIP: consider replacing the test server initialization from:
    ts, ... := serverutils.StartServer(t, ...)
    defer ts.Stopper().Stop(...)
to:
    srv, ... := serverutils.StartServer(t, ...)
    defer srv.Stopper().Stop(...)
    ts := srv.ApplicationLayer()

See also: https://go.crdb.dev/p/testserver-and-cluster-virtualization
    testutils.go:286: no Invalid Descriptors
=== RUN   TestBackupCheckpointing/inc-backup
    test_server_shim.go:154: automatically injected an external process virtual cluster under test; see comment at top of test_server_shim.go for details.

pkg/ccl/backupccl/backup_test.go:1554: (TestBackupCheckpointing.func5)
	NOTICE: .ExecutorConfig() called via implicit interface ApplicationLayerInterface;
HINT: consider using .ApplicationLayer().ExecutorConfig() instead.
TIP: consider replacing the test server initialization from:
    ts, ... := serverutils.StartServer(t, ...)
    defer ts.Stopper().Stop(...)
to:
    srv, ... := serverutils.StartServer(t, ...)
    defer srv.Stopper().Stop(...)
    ts := srv.ApplicationLayer()

See also: https://go.crdb.dev/p/testserver-and-cluster-virtualization
    testutils.go:286: no Invalid Descriptors
=== RUN   TestBackupCheckpointing/introduce-spans
    test_server_shim.go:154: automatically injected an external process virtual cluster under test; see comment at top of test_server_shim.go for details.

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-48123

@cockroach-teamcity cockroach-teamcity added branch-release-23.2 Used to mark GA and release blockers, technical advisories, and bugs for 23.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 Feb 26, 2025
@cockroach-teamcity cockroach-teamcity added this to the 23.2 milestone Feb 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-disaster-recovery branch-release-23.2 Used to mark GA and release blockers, technical advisories, and bugs for 23.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