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: TestImportFixture failed #125329

Closed
cockroach-teamcity opened this issue Jun 7, 2024 · 1 comment · Fixed by #125357
Closed

pkg/ccl/workloadccl/workloadccl_test: TestImportFixture failed #125329

cockroach-teamcity opened this issue Jun 7, 2024 · 1 comment · Fixed by #125357
Assignees
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-queries SQL Queries Team

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented Jun 7, 2024

pkg/ccl/workloadccl/workloadccl_test.TestImportFixture failed with artifacts on master @ e2ddbb469ff4b38f1b38210514eed802073779ed:

                        sort-all-1-unlimited-2 0 B
                        sort-all-1-limited-1 0 B
                        cfetcher-0-unlimited-0 10 KiB
                session 20 KiB
                    session prepared statements 8.0 KiB
 [recovered]
	panic: found 9 short-living non-stopped monitors in root
root 1.0 MiB (256 MiB / 0 B)
            session root 30 KiB
                txn 10 KiB
                    flow 6b2f5555 10 KiB
                        external-sorter-1-unlimited-3 0 B
                        sort-all-1-unlimited-2 0 B
                        sort-all-1-limited-1 0 B
                        cfetcher-0-unlimited-0 10 KiB
                session 20 KiB
                    session prepared statements 8.0 KiB


goroutine 15 [running]:
testing.tRunner.func1.2({0x58b1500, 0x4006b2b6a0})
	GOROOT/src/testing/testing.go:1631 +0x1c4
testing.tRunner.func1()
	GOROOT/src/testing/testing.go:1634 +0x33c
panic({0x58b1500?, 0x4006b2b6a0?})
	GOROOT/src/runtime/panic.go:770 +0x124
github.com/cockroachdb/cockroach/pkg/util/leaktest.AfterTest.func2()
	github.com/cockroachdb/cockroach/pkg/util/leaktest/leaktest.go:133 +0x370
panic({0x58b1500?, 0x4006b2b6a0?})
	GOROOT/src/runtime/panic.go:770 +0x124
github.com/cockroachdb/cockroach/pkg/util/stop.(*Stopper).recover(0x40026dafc8?, {0x77bb228, 0xb71e1c0})
	github.com/cockroachdb/cockroach/pkg/util/stop/stopper.go:231 +0x68
panic({0x58b1500?, 0x4006b2b6a0?})
	GOROOT/src/runtime/panic.go:770 +0x124
github.com/cockroachdb/cockroach/pkg/util/mon.(*BytesMonitor).doStop(0x4000167cc0, {0x77bb3b0, 0x4001e47b60}, 0x0)
	github.com/cockroachdb/cockroach/pkg/util/mon/bytes_usage.go:657 +0x57c
github.com/cockroachdb/cockroach/pkg/util/mon.(*BytesMonitor).EmergencyStop(...)
	github.com/cockroachdb/cockroach/pkg/util/mon/bytes_usage.go:593
github.com/cockroachdb/cockroach/pkg/server.NewServer.func10()
	github.com/cockroachdb/cockroach/pkg/server/server.go:722 +0x30
github.com/cockroachdb/cockroach/pkg/util/stop.CloserFn.Close(0x400513d9c8?)
	github.com/cockroachdb/cockroach/pkg/util/stop/stopper.go:108 +0x24
github.com/cockroachdb/cockroach/pkg/util/stop.(*Stopper).Stop(0x4003e12ea0, {0x77bb228, 0xb71e1c0})
	github.com/cockroachdb/cockroach/pkg/util/stop/stopper.go:550 +0x108
pkg/ccl/workloadccl/workloadccl_test_test.TestImportFixture(0x4004f09a00)
	pkg/ccl/workloadccl/workloadccl_test_test/pkg/ccl/workloadccl/fixture_test.go:235 +0x724
testing.tRunner(0x4004f09a00, 0x6344bb8)
	GOROOT/src/testing/testing.go:1689 +0xec
created by testing.(*T).Run in goroutine 1
	GOROOT/src/testing/testing.go:1742 +0x318
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-39383

@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-sql-foundations SQL Foundations Team (formerly SQL Schema + SQL Sessions) T-testeng TestEng Team labels Jun 7, 2024
@rafiss
Copy link
Collaborator

rafiss commented Jun 7, 2024

	panic: found 9 short-living non-stopped monitors in root

could be related to #125004, cc @yuzefovich

@rafiss rafiss added T-sql-queries SQL Queries Team and removed T-sql-foundations SQL Foundations Team (formerly SQL Schema + SQL Sessions) labels Jun 7, 2024
@github-project-automation github-project-automation bot moved this to Triage in SQL Queries Jun 7, 2024
@yuzefovich yuzefovich removed release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. T-testeng TestEng Team labels Jun 7, 2024
@yuzefovich yuzefovich self-assigned this Jun 7, 2024
@yuzefovich yuzefovich moved this from Triage to Active in SQL Queries Jun 7, 2024
@craig craig bot closed this as completed in f5e65c5 Jun 12, 2024
@github-project-automation github-project-automation bot moved this from Active to Done in SQL Queries Jun 12, 2024
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-queries SQL Queries Team
Projects
Archived in project
3 participants