cockroachdb / cockroachdb/cockroach
basalt-26.3.2-rc-20260908: testutils/testcluster: TestClusterSqlDisabled failed
Open
Nobody has claimed this yet.
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 on basalt-26.3.2-rc-20260908 @ 807558e5e81666af257c811e925e4cae570abc28:
=== RUN TestClusterSqlDisabled
test_log_scope.go:172: test logs captured to: outputs.zip/logTestClusterSqlDisabled1743953313
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=1race=truerun=2shard=2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with testutils/testcluster.TestClusterSqlDisabled and the linked EngFlow test report, then inspect the captured logs for the failing disable-sql=false/test-tenant={1_true_false_0_} case. Reproduce the failure with the reported race configuration and commit if possible; done means the test passes reliably and the failure cause is addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100