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.

Sign up for GitHub

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

Jump to bottom

crosscluster/physical: TestReaderTenantCutover failed #143060

Open
cockroach-teamcity opened this issue Mar 18, 2025 · 2 comments
Open

crosscluster/physical: TestReaderTenantCutover failed #143060

cockroach-teamcity opened this issue Mar 18, 2025 · 2 comments
Assignees
@msbutler
Labels
A-disaster-recovery branch-release-25.1.3-rc C-test-failure Broken test (automatically or manually discovered). O-robot Originated from a bot. P-2 Issues/test failures with a fix SLA of 3 months 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 Mar 18, 2025 •
edited by cockroach-jira-scripts
Loading

crosscluster/physical.TestReaderTenantCutover failed on release-25.1.3-rc @ 89ce402f3e337ec547bac75d63438201b5f6ba19:

=== RUN   TestReaderTenantCutover
    test_log_scope.go:165: test logs captured to: outputs.zip/logTestReaderTenantCutover757051553
    test_log_scope.go:76: use -show-logs to present logs inline
    standby_read_ts_poller_job_test.go:284: -- test log scope end --
test logs left over in: outputs.zip/logTestReaderTenantCutover757051553
--- FAIL: TestReaderTenantCutover (119.70s)
=== RUN   TestReaderTenantCutover/cutoverToLatest=false
    testutils.go:603: waited for 5.19966481s to advance to 1742294495.987366023,0
    testutils.go:603: waited for 1.983907736s to advance to 1742294514.649365909,0
    standby_read_ts_poller_job_test.go:110: error scanning '&{0xc00c41cfc0 <nil>}': pq: database "defaultdb" does not exist
    --- FAIL: TestReaderTenantCutover/cutoverToLatest=false (43.34s)

Parameters:

  • attempt=1
  • race=true
  • run=2
  • shard=15
Help

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

Same failure on other branches

/cc @cockroachdb/disaster-recovery

This test on roachdash | Improve this report!

Jira issue: CRDB-48641
@cockroach-teamcity cockroach-teamcity added branch-release-25.1.3-rc 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 Mar 18, 2025
@cockroach-teamcity
Copy link
Member Author

crosscluster/physical.TestReaderTenantCutover failed on release-25.1.3-rc @ e5022b9fa6fd707e20daa4ae7e0a842bd8ce35cf:

Fatal error:

panic: test timed out after 53m20s
running tests:
	TestReaderTenantCutover (52m51s)
	TestReaderTenantCutover/cutoverToLatest=true (52m5s)

Stack:

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

=== RUN   TestReaderTenantCutover
    test_log_scope.go:165: test logs captured to: outputs.zip/logTestReaderTenantCutover2484723493
    test_log_scope.go:76: use -show-logs to present logs inline
=== RUN   TestReaderTenantCutover/cutoverToLatest=false
    testutils.go:603: waited for 6.08639678s to advance to 1742469765.174144190,0
    testutils.go:603: waited for 4.216294738s to advance to 1742469782.128749381,0
=== RUN   TestReaderTenantCutover/cutoverToLatest=true
    testutils.go:603: waited for 3.720494371s to advance to 1742469813.163529152,0

Parameters:

  • attempt=1
  • race=true
  • run=2
  • shard=15
Help

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

Same failure on other branches

This test on roachdash | Improve this report!

@jeffswenson
Copy link
Collaborator

This is fixed on the base release branch.

@exalate-issue-sync exalate-issue-sync bot reopened this Mar 24, 2025
@exalate-issue-sync exalate-issue-sync bot added the P-2 Issues/test failures with a fix SLA of 3 months label Mar 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@msbutler msbutler

Labels
A-disaster-recovery branch-release-25.1.3-rc C-test-failure Broken test (automatically or manually discovered). O-robot Originated from a bot. P-2 Issues/test failures with a fix SLA of 3 months 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
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jeffswenson @cockroach-teamcity @msbutler