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/logical: TestUDFInsertOnly failed #138667

Open
cockroach-teamcity opened this issue Jan 8, 2025 · 0 comments
Open

crosscluster/logical: TestUDFInsertOnly failed #138667

cockroach-teamcity opened this issue Jan 8, 2025 · 0 comments
Labels
A-disaster-recovery branch-master Failures and bugs on the master branch. 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 Jan 8, 2025

crosscluster/logical.TestUDFInsertOnly failed with artifacts on master @ cc415988cfaa6099bea46a30c652fe1840a04b68:

Fatal error:

panic: test timed out after 5m0s
running tests:
	TestUDFInsertOnly (1s)

Stack:

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

=== RUN   TestUDFInsertOnly
    test_log_scope.go:165: test logs captured to: /artifacts/tmp/_tmp/1d763551fab9a9ec1181b9c428b68cea/logTestUDFInsertOnly1437313402
    test_log_scope.go:76: use -show-logs to present logs inline
    test_server_shim.go:88: cluster virtualization disabled due to issue: #127241 (expected label: C-bug)

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

@cockroach-teamcity cockroach-teamcity added branch-master Failures and bugs on the master branch. 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 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-disaster-recovery branch-master Failures and bugs on the master branch. 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