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

pkg/ccl/workloadccl/workloadccl_test: TestImportFixtureNodeCount failed #108256

Closed
cockroach-teamcity opened this issue Aug 6, 2023 · 2 comments
Labels
branch-master Failures and bugs on the master branch. C-test-failure Broken test (automatically or manually discovered). O-robot Originated from a bot. T-sql-foundations SQL Foundations Team (formerly SQL Schema + SQL Sessions)
Milestone

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented Aug 6, 2023

pkg/ccl/workloadccl/workloadccl_test.TestImportFixtureNodeCount failed with artifacts on master @ f1623e0a2cffc81580ee3c3b71035efd854d89c9:

Fatal error:

panic: test timed out after 55s

Stack:

goroutine 43195 [running]:
testing.(*M).startAlarm.func1()
	GOROOT/src/testing/testing.go:2036 +0x8e
created by time.goFunc
	GOROOT/src/time/sleep.go:176 +0x32
Log preceding fatal error

=== RUN   TestImportFixtureNodeCount
    test_log_scope.go:167: test logs captured to: /artifacts/tmp/_tmp/fd719ddfcba889d931fc8ef278f553b7/logTestImportFixtureNodeCount1798949547
    test_log_scope.go:81: use -show-logs to present logs inline
    test_server_shim.go:98: 
        Test server was configured to route SQL queries to a secondary tenant (virtual cluster).
        If you are only seeing a test failure when this message appears, there may be a problem
        specific to cluster virtualization or multi-tenancy.
        
        To investigate, consider using "COCKROACH_TEST_TENANT=true" to force-enable just
        the secondary tenant in all runs (or, alternatively, "false" to force-disable), or use
        "COCKROACH_INTERNAL_DISABLE_METAMORPHIC_TESTING=false" to disable all random test variables altogether.
    testcluster.go:416: 
        Test server was configured to route SQL queries to a secondary tenant (virtual cluster).
        If you are only seeing a test failure when this message appears, there may be a problem
        specific to cluster virtualization or multi-tenancy.
        
        To investigate, consider using "COCKROACH_TEST_TENANT=true" to force-enable just
        the secondary tenant in all runs (or, alternatively, "false" to force-disable), or use
        "COCKROACH_INTERNAL_DISABLE_METAMORPHIC_TESTING=false" to disable all random test variables altogether.

Help

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

/cc @cockroachdb/test-eng @cockroachdb/sql-foundations

This test on roachdash | Improve this report!

Jira issue: CRDB-30389

@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. T-sql-foundations SQL Foundations Team (formerly SQL Schema + SQL Sessions) T-testeng TestEng Team labels Aug 6, 2023
@cockroach-teamcity cockroach-teamcity added this to the 23.2 milestone Aug 6, 2023
@otan
Copy link
Contributor

otan commented Aug 7, 2023

on bors: #107918 (comment)

@rafiss
Copy link
Collaborator

rafiss commented Aug 7, 2023

@rafiss rafiss closed this as completed Aug 7, 2023
@exalate-issue-sync exalate-issue-sync bot removed the T-testeng TestEng Team label Aug 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch-master Failures and bugs on the master branch. C-test-failure Broken test (automatically or manually discovered). O-robot Originated from a bot. T-sql-foundations SQL Foundations Team (formerly SQL Schema + SQL Sessions)
Projects
None yet
Development

No branches or pull requests

3 participants