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

crosscluster/physical: TestReaderTenantCutover failed #141984

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

crosscluster/physical: TestReaderTenantCutover failed #141984

cockroach-teamcity opened this issue Feb 25, 2025 · 0 comments
Labels
A-disaster-recovery branch-release-25.1.0-rc Used to mark GA and release blockers and technical advisories for 25.1.0-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

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented Feb 25, 2025

crosscluster/physical.TestReaderTenantCutover failed on release-25.1.0-rc @ e5ec46c9865849c0b20ffa1b351372ced6c578b4:

Fatal error:

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

Stack:

goroutine 630146 [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/logTestReaderTenantCutover3630434392
    test_log_scope.go:76: use -show-logs to present logs inline
=== RUN   TestReaderTenantCutover/cutoverToLatest=false
    testutils.go:603: waited for 3.858626168s to advance to 1740483009.176896424,0
    testutils.go:603: waited for 2.800261132s to advance to 1740483023.549833919,0
=== RUN   TestReaderTenantCutover/cutoverToLatest=true
    testutils.go:603: waited for 3.030966871s to advance to 1740483049.089476472,0

Parameters:

  • attempt=1
  • race=true
  • run=3
  • 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-48109

@cockroach-teamcity cockroach-teamcity added branch-release-25.1.0-rc Used to mark GA and release blockers and technical advisories for 25.1.0-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 Feb 25, 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.0-rc Used to mark GA and release blockers and technical advisories for 25.1.0-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
Projects
None yet
Development

No branches or pull requests

1 participant