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

pkg/ccl/testccl/sqlccl/sqlccl_test: TestExplainGist failed #130764

Closed
cockroach-teamcity opened this issue Sep 15, 2024 · 2 comments
Closed

pkg/ccl/testccl/sqlccl/sqlccl_test: TestExplainGist failed #130764

cockroach-teamcity opened this issue Sep 15, 2024 · 2 comments
Assignees
@rytaft
Labels
branch-release-24.2.3-rc C-test-failure Broken test (automatically or manually discovered). O-robot Originated from a bot. P-1 Issues/test failures with a fix SLA of 1 month release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. T-sql-queries SQL Queries Team X-duplicate Closed as a duplicate of another issue.

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented Sep 15, 2024 •
edited by cockroach-jira-scripts
Loading

pkg/ccl/testccl/sqlccl/sqlccl_test.TestExplainGist failed on release-24.2.3-rc @ 7af073299909f1ba050f2c7fe28d8df02d7fb30a:

Fatal error:

panic: found 1 short-living non-stopped monitors in root
root 1.7 MiB (256 MiB / 0 B)
            index-backfill-mon 0 B
 [recovered]
	panic: found 1 short-living non-stopped monitors in root
root 1.7 MiB (256 MiB / 0 B)
            index-backfill-mon 0 B
 [recovered]
	panic: found 1 short-living non-stopped monitors in root
root 1.7 MiB (256 MiB / 0 B)
            index-backfill-mon 0 B

Stack:

goroutine 22 [running]:
testing.tRunner.func1.2({0x64ff000, 0xc01199db70})
	GOROOT/src/testing/testing.go:1631 +0x24a
testing.tRunner.func1()
	GOROOT/src/testing/testing.go:1634 +0x377
panic({0x64ff000?, 0xc01199db70?})
	GOROOT/src/runtime/panic.go:770 +0x132
github.com/cockroachdb/cockroach/pkg/util/stop.(*Stopper).recover(0x112708a?, {0x853c668, 0xcc98e40})
	github.com/cockroachdb/cockroach/pkg/util/stop/stopper.go:231 +0x65
panic({0x64ff000?, 0xc01199db70?})
	GOROOT/src/runtime/panic.go:770 +0x132
github.com/cockroachdb/cockroach/pkg/util/mon.(*BytesMonitor).doStop(0xc005626640, {0x853c838, 0xc0015199e0}, 0x0)
	github.com/cockroachdb/cockroach/pkg/util/mon/bytes_usage.go:657 +0x653
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:724 +0x25
github.com/cockroachdb/cockroach/pkg/util/stop.CloserFn.Close(0xc0053ac408?)
	github.com/cockroachdb/cockroach/pkg/util/stop/stopper.go:108 +0x12
github.com/cockroachdb/cockroach/pkg/util/stop.(*Stopper).Stop(0xc0053a8510, {0x853c668, 0xcc98e40})
	github.com/cockroachdb/cockroach/pkg/util/stop/stopper.go:550 +0x131
pkg/ccl/testccl/sqlccl/sqlccl_test.TestExplainGist.func1(0xc0051cda00)
	pkg/ccl/testccl/sqlccl/sqlccl_test/pkg/ccl/testccl/sqlccl/explain_test.go:300 +0x9a5
testing.tRunner(0xc0051cda00, 0xc0015195c0)
	GOROOT/src/testing/testing.go:1689 +0xfb
created by testing.(*T).Run in goroutine 16
	GOROOT/src/testing/testing.go:1742 +0x390
Log preceding fatal error 

=== RUN   TestExplainGist
    test_log_scope.go:170: test logs captured to: outputs.zip/logTestExplainGist2643854250
    test_log_scope.go:81: use -show-logs to present logs inline
--- FAIL: TestExplainGist (7.67s)
=== RUN   TestExplainGist/main
*
* ERROR: a panic has occurred!
* found 1 short-living non-stopped monitors in root
* (1) attached stack trace
*   -- stack trace:
*   | runtime.gopanic
*   | 	GOROOT/src/runtime/panic.go:770
*   | [...repeated from below...]
* Wraps: (2) assertion failure
* Wraps: (3) attached stack trace
*   -- stack trace:
*   | github.com/cockroachdb/cockroach/pkg/util/mon.(*BytesMonitor).doStop
*   | 	github.com/cockroachdb/cockroach/pkg/util/mon/bytes_usage.go:657
*   | 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:724
*   | github.com/cockroachdb/cockroach/pkg/util/stop.CloserFn.Close
*   | 	github.com/cockroachdb/cockroach/pkg/util/stop/stopper.go:108
*   | github.com/cockroachdb/cockroach/pkg/util/stop.(*Stopper).Stop
*   | 	github.com/cockroachdb/cockroach/pkg/util/stop/stopper.go:550
*   | pkg/ccl/testccl/sqlccl/sqlccl_test.TestExplainGist.func1
*   | 	pkg/ccl/testccl/sqlccl/sqlccl_test/pkg/ccl/testccl/sqlccl/explain_test.go:300
*   | testing.tRunner
*   | 	GOROOT/src/testing/testing.go:1689
*   | runtime.goexit
*   | 	src/runtime/asm_amd64.s:1695
* Wraps: (4) found 1 short-living non-stopped monitors in root
*   | root 1.7 MiB (256 MiB / 0 B)
*   |             index-backfill-mon 0 B
* Error types: (1) *withstack.withStack (2) *assert.withAssertionFailure (3) *withstack.withStack (4) *errutil.leafError
*
    --- FAIL: TestExplainGist/main (7.66s)

Parameters:

  • attempt=1
  • run=2
  • shard=2
Help

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

Same failure on other branches

This test on roachdash | Improve this report!

Jira issue: CRDB-42215
@cockroach-teamcity cockroach-teamcity added branch-release-24.2.3-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-sql-queries SQL Queries Team labels Sep 15, 2024
@github-project-automation github-project-automation bot moved this to Triage in SQL Queries Sep 15, 2024
@cockroach-teamcity cockroach-teamcity mentioned this issue Sep 18, 2024
Closed
@cockroach-teamcity
Copy link
Member Author

pkg/ccl/testccl/sqlccl/sqlccl_test.TestExplainGist failed on release-24.2.3-rc @ 47646613d54c7a68e8c4a2468092e147461b09c5:

        	2:::INT8;
        UPDATE
        	defaultdb.public.seed AS tab_402
        SET
        	_enum = tab_405._enum
        FROM
        	defaultdb.public.seed AS tab_403,
        	defaultdb.public.seed AS tab_404,
        	defaultdb.public.seed AS tab_405,
        	defaultdb.public.seed AS tab_406,
        	defaultdb.public.seed AS tab_407,
        	defaultdb.public.seed AS tab_408,
        	defaultdb.public.seed AS tab_409,
        	defaultdb.public.seed AS tab_410;
        UPDATE
        	defaultdb.public.seed AS tab_411
        SET
        	_decimal = 0:::DECIMAL
        WHERE
        	NULL
        ORDER BY
        	tab_411._bytes ASC
        LIMIT
        	37:::INT8;
        UPDATE
        	defaultdb.public.seed AS tab_412
        SET
        	_decimal = tab_413._decimal,
        	_float4 = 0.8832246661186218:::FLOAT8,
        	_jsonb = tab_413._jsonb,
        	_int8
        		= ((tab_413._inet::INET - 'ba4f:4040:5159:f104:1583:60a9:8b07:c3c/90':::INET::INET)::INT8::INT8 - tab_412._int4::INT8)::INT8,
        	_date = date(tab_413._timestamptz::TIMESTAMPTZ)::DATE
        FROM
        	defaultdb.public.seed AS tab_413
        WHERE
        	NULL
        LIMIT
        	50:::INT8;
        ALTER TABLE defaultdb.public.seed ALTER COLUMN _timestamp SET DATA TYPE TIMESTAMPTZ;
        
    explain_test.go:204: pq: internal error: type check failed while initializing stat 1005421905666801665: histogram for table seed column _timestamp created_at 2024-09-21 06:40:15.523894 does not match column type TIMESTAMPTZ: TIMESTAMP: UPDATE
        	defaultdb.public.seed AS tab_415
        SET
        	_date = tab_415._date,
        	_timestamptz = tab_415._timestamptz,
        	_bool = tab_415._bool,
        	_int4 = (-357311462):::INT8,
        	_float8 = (-0.5277838614017445):::FLOAT8
    --- FAIL: TestExplainGist/main (4.72s)

Parameters:

  • attempt=1
  • run=10
  • shard=2
Help

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

Same failure on other branches

This test on roachdash | Improve this report!

@rytaft rytaft self-assigned this Oct 2, 2024
@rytaft rytaft added P-1 Issues/test failures with a fix SLA of 1 month X-duplicate Closed as a duplicate of another issue. labels Oct 2, 2024
@rytaft
Copy link
Collaborator

rytaft commented Oct 2, 2024

Dup of #130755

@rytaft rytaft closed this as completed Oct 2, 2024
@github-project-automation github-project-automation bot moved this from Triage to Done in SQL Queries Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rytaft rytaft

Labels
branch-release-24.2.3-rc C-test-failure Broken test (automatically or manually discovered). O-robot Originated from a bot. P-1 Issues/test failures with a fix SLA of 1 month release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. T-sql-queries SQL Queries Team X-duplicate Closed as a duplicate of another issue.
Projects
SQL Queries
Archived in project
Milestone
No milestone
Development

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