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

backup: TestBackupSharedProcessTenantNodeDown failed #139778

Open
cockroach-teamcity opened this issue Jan 24, 2025 · 0 comments
Open

backup: TestBackupSharedProcessTenantNodeDown failed #139778

cockroach-teamcity opened this issue Jan 24, 2025 · 0 comments
Labels
A-disaster-recovery branch-release-25.1 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 Jan 24, 2025

backup.TestBackupSharedProcessTenantNodeDown failed on release-25.1 @ 98ef65420f236cb16e7d88767ce3e38eab1e9b54:

=== RUN   TestBackupSharedProcessTenantNodeDown
I250124 16:33:23.840313 1 (gostd) rand.go:246  [-] 1  random seed: 7400481297899205761
    test_log_scope.go:165: test logs captured to: outputs.zip/logTestBackupSharedProcessTenantNodeDown3161315014
    test_log_scope.go:76: use -show-logs to present logs inline
    backup_tenant_test.go:78: waiting for SQL instances
    backup_tenant_test.go:82: waiting for server 1
    backup_tenant_test.go:82: waiting for server 1
    backup_tenant_test.go:82: waiting for server 1
    backup_tenant_test.go:82: waiting for server 1
    backup_tenant_test.go:82: waiting for server 1
    backup_tenant_test.go:82: waiting for server 1
    backup_tenant_test.go:82: waiting for server 1
    backup_tenant_test.go:82: waiting for server 1
    backup_tenant_test.go:82: waiting for server 1
    backup_tenant_test.go:82: waiting for server 1
    backup_tenant_test.go:82: waiting for server 1
    backup_tenant_test.go:82: waiting for server 1
    backup_tenant_test.go:82: waiting for server 1
    backup_tenant_test.go:82: waiting for server 1
    backup_tenant_test.go:82: waiting for server 1
    backup_tenant_test.go:82: waiting for server 1
    backup_tenant_test.go:82: waiting for server 1
    backup_tenant_test.go:82: waiting for server 1
    backup_tenant_test.go:82: waiting for server 1
    backup_tenant_test.go:82: waiting for server 1
    backup_tenant_test.go:82: waiting for server 1
    backup_tenant_test.go:82: waiting for server 1
    backup_tenant_test.go:82: waiting for server 1
    backup_tenant_test.go:82: waiting for server 1
    backup_tenant_test.go:82: waiting for server 1
    backup_tenant_test.go:82: waiting for server 1
    backup_tenant_test.go:82: waiting for server 1
    backup_tenant_test.go:82: waiting for server 1
    backup_tenant_test.go:82: waiting for server 1
    backup_tenant_test.go:82: waiting for server 2
    backup_tenant_test.go:90: all SQL instances (took 474.899121ms)
    backup_tenant_test.go:93: shutting down server 2 (n3)
    backup_tenant_test.go:101: condition failed to evaluate within 12.25s: pq: job 1040928014941421569: node liveness error: restarting in background
    testutils.go:296: no Invalid Descriptors
    panic.go:626: -- test log scope end --
test logs left over in: outputs.zip/logTestBackupSharedProcessTenantNodeDown3161315014
--- FAIL: TestBackupSharedProcessTenantNodeDown (25.80s)

Parameters:

  • attempt=1
  • run=24
  • shard=17
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-46807

@cockroach-teamcity cockroach-teamcity added branch-release-25.1 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 Jan 24, 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-25.1 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