backup: TestScheduleChainingWithDatabaseExpansion failed

[cockroach-teamcity]

backup.TestScheduleChainingWithDatabaseExpansion failed on release-25.2 @ ead527fe7992d26a27010e2cc30362ff14837069:

=== RUN   TestScheduleChainingWithDatabaseExpansion
    test_log_scope.go:165: test logs captured to: outputs.zip/logTestScheduleChainingWithDatabaseExpansion3672668340
    test_log_scope.go:76: use -show-logs to present logs inline
    schedule_pts_chaining_test.go:436: condition failed to evaluate within 3m45s: sql: no rows in result set
    panic.go:635: -- test log scope end --
test logs left over in: outputs.zip/logTestScheduleChainingWithDatabaseExpansion3672668340
--- FAIL: TestScheduleChainingWithDatabaseExpansion (307.33s)

Parameters:

• attempt=1
• race=true
• run=3
• shard=11

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

[cockroach-teamcity]

backup.TestScheduleChainingWithDatabaseExpansion failed on release-25.2 @ a25a36211e8d14ac4b26d22d586243042af79bfb:

=== RUN   TestScheduleChainingWithDatabaseExpansion
    test_log_scope.go:165: test logs captured to: outputs.zip/logTestScheduleChainingWithDatabaseExpansion908099243
    test_log_scope.go:76: use -show-logs to present logs inline
    schedule_pts_chaining_test.go:436: condition failed to evaluate within 3m45s: sql: no rows in result set
    panic.go:635: -- test log scope end --
test logs left over in: outputs.zip/logTestScheduleChainingWithDatabaseExpansion908099243
--- FAIL: TestScheduleChainingWithDatabaseExpansion (255.09s)

Parameters:

• attempt=1
• race=true
• run=3
• shard=11

Help

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

This test on roachdash | Improve this report!