Skip to content

backup: TestBackupSharedProcessTenantNodeDown failed #162523

@cockroach-teamcity

Description

@cockroach-teamcity

backup.TestBackupSharedProcessTenantNodeDown failed on release-26.1 @ 0f99c31f3e7f5172c5827b6f727fcd432bd731db:

=== RUN   TestBackupSharedProcessTenantNodeDown
    test_log_scope.go:171: test logs captured to: outputs.zip/logTestBackupSharedProcessTenantNodeDown3593085906
    test_log_scope.go:82: use -show-logs to present logs inline
    backup_tenant_test.go:76: waiting for SQL instances
    backup_tenant_test.go:80: waiting for server 1
    backup_tenant_test.go:80: waiting for server 1
    backup_tenant_test.go:80: waiting for server 2
    backup_tenant_test.go:88: all SQL instances (took 38.114037ms)
    backup_tenant_test.go:91: shutting down server 2 (n3)
    backup_tenant_test.go:99: condition failed to evaluate within 12.25s: pq: job 1147550109473570817: could not mark as reverting: job 1147550109473570817: with state "running": expected session "0101804e671caaacde4c76bb779c8a443725f1" but found NULL
    testutils.go:307: no Invalid Descriptors
    panic.go:615: -- test log scope end --
test logs left over in: outputs.zip/logTestBackupSharedProcessTenantNodeDown3593085906
--- FAIL: TestBackupSharedProcessTenantNodeDown (31.18s)

Parameters:

  • attempt=1
  • run=7
  • shard=18
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-59515

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-disaster-recoveryC-test-failureBroken test (automatically or manually discovered).O-robotOriginated from a bot.T-disaster-recoverybranch-release-26.1Used to mark GA and release blockers, technical advisories, and bugs for 26.1release-blockerIndicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions