cockroachdb / cockroachdb/cockroach

basalt-26.3.2-rc-20260908: testutils/testcluster: TestClusterSqlDisabled failed

Open
#175,553 2 comments 0 reactions 0 assignees View on GitHub
branch-basalt-26.3.2-rc-20260908 C-test-failure O-robot release-blocker T-testeng
Dominant language
Go
Stars
32.5k
Forks
4.1k
PR merge metrics
PR metrics pending

Description

testutils/testcluster.TestClusterSqlDisabled [failed](https://mesolite.cluster.engflow.com/invocations/default/84483de1-b344-4bb7-a487-42863798b484?testReportRun=3&testReportShard=2&testReportAttempt=1#targets-Ly9wa2cvdGVzdHV0aWxzL3Rlc3RjbHVzdGVyOnRlc3RjbHVzdGVyX3Rlc3Q=) on basalt-26.3.2-rc-20260908 @ [807558e5e81666af257c811e925e4cae570abc28](https://github.com/cockroachdb/cockroach/commits/807558e5e81666af257c811e925e4cae570abc28):

```
=== RUN TestClusterSqlDisabled
test_log_scope.go:172: test logs captured to: outputs.zip/logTestClusterSqlDisabled1304108496
test_log_scope.go:82: use -show-logs to present logs inline
=== RUN TestClusterSqlDisabled/disable-sql=false
=== RUN TestClusterSqlDisabled/disable-sql=false/test-tenant={1_true_false_0_}
```

Parameters:
- attempt=1
- race=true
- run=3
- shard=2
Help

See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)

/cc @cockroachlabs/test-eng

[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestClusterSqlDisabled.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/bazci/githubpost/issues)

Contributor guide

Open the contributing guide

Research direction

Start with testutils/testcluster.TestClusterSqlDisabled and inspect the linked test report and captured log path for the failure at commit 807558e5e81666af257c811e925e4cae570abc28. Re-run the test with the reported race, run, and shard parameters, then identify why the disable-sql=false tenant case fails. Done means the test passes reliably on the basalt-26.3.2-rc-20260908 configuration.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, sql
Domain
databases, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.