cockroachdb / cockroachdb/cockroach

basalt-26.3.2-rc-20260908: sql/tests: TestClusterID failed

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

Description

sql/tests.TestClusterID [failed](https://mesolite.cluster.engflow.com/invocations/default/f0916551-4348-4015-a964-7d1ed87aeec5?testReportRun=1&testReportShard=4&testReportAttempt=1#targets-Ly9wa2cvc3FsL3Rlc3RzOnRlc3RzX3Rlc3Q=) on basalt-26.3.2-rc-20260908 @ [807558e5e81666af257c811e925e4cae570abc28](https://github.com/cockroachdb/cockroach/commits/807558e5e81666af257c811e925e4cae570abc28):

```
=== RUN TestClusterID
test_log_scope.go:172: test logs captured to: outputs.zip/logTestClusterID1633625209
test_log_scope.go:82: use -show-logs to present logs inline
test_server_shim.go:168: automatically injected an external process virtual cluster under test; see comment at top of test_server_shim.go for details.
```

Parameters:
- attempt=1
- race=true
- run=1
- shard=4
Help

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

Same failure on other branches

- #174784 basalt-26.3: sql/tests: TestClusterID failed [C-test-failure O-robot T-sql-queries branch-basalt-26.3]

[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestClusterID.*&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 the linked Mesolite invocation and the sql/tests.TestClusterID failure report, then read the referenced test_server_shim.go comment about the injected external process virtual cluster. Compare the failure with issue #174784 and reproduce the test with race=true if possible. Done means identifying and fixing the cause so TestClusterID passes on the affected branch.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, sql
Domain
databases, testing
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.