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/serverccl/statusccl/statusccl_test: TestTenantStatusAPI failed #103381

Closed
cockroach-teamcity opened this issue May 16, 2023 · 1 comment
Closed
Labels
C-test-failure Broken test (automatically or manually discovered). O-robot Originated from a bot. T-multitenant Issues owned by the multi-tenant virtual team
Milestone

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented May 16, 2023

pkg/ccl/serverccl/statusccl/statusccl_test.TestTenantStatusAPI failed with artifacts on release-23.1.0 @ 358e0d87912365b8976c55ab9b3292e999cf720d:

=== RUN   TestTenantStatusAPI
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/8bc2de686563d04c3522b0df244fc129/logTestTenantStatusAPI3679121546
=== CONT  TestTenantStatusAPI
    tenant_status_test.go:141: -- test log scope end --
CREATE UNIQUE INDEX test_pkey ON test_db1.public.test USING btree (k ASC)test logs left over in: /artifacts/tmp/_tmp/8bc2de686563d04c3522b0df244fc129/logTestTenantStatusAPI3679121546
--- FAIL: TestTenantStatusAPI (45.31s)
=== RUN   TestTenantStatusAPI/tenant_span_stats
    --- FAIL: TestTenantStatusAPI/tenant_span_stats (0.86s)
=== RUN   TestTenantStatusAPI/tenant_span_stats/test_KV_node_fan-out
    tenant_status_test.go:247: 
        	Error Trace:	pkg/ccl/serverccl/statusccl/statusccl_test/pkg/ccl/serverccl/statusccl/tenant_status_test.go:247
        	Error:      	Not equal: 
        	            	expected: 878
        	            	actual  : 876
        	Test:       	TestTenantStatusAPI/tenant_span_stats/test_KV_node_fan-out
        --- FAIL: TestTenantStatusAPI/tenant_span_stats/test_KV_node_fan-out (0.38s)

Parameters: TAGS=bazel,gss,deadlock

Help

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

Same failure on other branches

/cc @cockroachdb/cluster-observability @cockroachdb/multi-tenant

This test on roachdash | Improve this report!

Jira issue: CRDB-27967

Epic CRDB-27931

@cockroach-teamcity cockroach-teamcity added branch-release-23.1.0 C-test-failure Broken test (automatically or manually discovered). O-robot Originated from a bot. T-multitenant Issues owned by the multi-tenant virtual team labels May 16, 2023
@cockroach-teamcity cockroach-teamcity added this to the 23.1 milestone May 16, 2023
@maryliag
Copy link
Contributor

closing since this is for 23.1.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-test-failure Broken test (automatically or manually discovered). O-robot Originated from a bot. T-multitenant Issues owned by the multi-tenant virtual team
Projects
None yet
Development

No branches or pull requests

2 participants