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/logical: TestLogicalReplicationCreationChecks failed #139947

Closed
github-actions bot opened this issue Jan 28, 2025 · 2 comments
Closed

crosscluster/logical: TestLogicalReplicationCreationChecks failed #139947

github-actions bot opened this issue Jan 28, 2025 · 2 comments
Assignees
@msbutler
Labels
A-disaster-recovery branch-release-25.1 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 T-disaster-recovery

Comments

@github-actions
Copy link

github-actions bot commented Jan 28, 2025 •
edited by cockroach-jira-scripts
Loading

crosscluster/logical.TestLogicalReplicationCreationChecks failed on release-25.1 @ 8a03c35cfdedee296787cd5bad33014a3b00f679:

Fatal error:

panic: test timed out after 5m0s
running tests:
	TestLogicalReplicationCreationChecks (1m5s)

Stack:

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

=== RUN   TestLogicalReplicationCreationChecks
    test_log_scope.go:165: test logs captured to: outputs.zip/logTestLogicalReplicationCreationChecks421730527
    test_log_scope.go:76: use -show-logs to present logs inline

Parameters:

  • attempt=1
  • run=1
  • shard=1
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-46930
@github-actions github-actions bot 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 28, 2025
@msbutler msbutler removed the release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. label Jan 29, 2025
@msbutler
Copy link
Collaborator

Likely resource exhaustion. Attempting to prevent via #139955

@msbutler msbutler added the P-2 Issues/test failures with a fix SLA of 3 months label Jan 29, 2025
@cockroach-teamcity
Copy link
Member

crosscluster/logical.TestLogicalReplicationCreationChecks failed on release-25.1 @ a53e619877e92319a0a26b9c6902751bd2024b2f:

Fatal error:

panic: test timed out after 5m0s
running tests:
	TestLogicalReplicationCreationChecks (1m9s)

Stack:

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

=== RUN   TestLogicalReplicationCreationChecks
    test_log_scope.go:165: test logs captured to: outputs.zip/logTestLogicalReplicationCreationChecks865760531
    test_log_scope.go:76: use -show-logs to present logs inline

Parameters:

  • attempt=1
  • run=22
  • shard=1
Help

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

This test on roachdash | Improve this report!

@msbutler msbutler closed this as completed Feb 5, 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 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 T-disaster-recovery
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cockroach-teamcity @msbutler