cockroachdb / cockroachdb/cockroach

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

Open
#175,658 2 comments 0 reactions 0 assignees View on GitHub

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 metrics pending

Description

testutils/testcluster.TestClusterStart failed on basalt-26.3.2-rc-20260908 @ 807558e5e81666af257c811e925e4cae570abc28:

=== RUN   TestClusterStart
    test_log_scope.go:172: test logs captured to: outputs.zip/logTestClusterStart160889276
    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=2
  • shard=1
Help

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

/cc @cockroachlabs/test-eng

This test on roachdash | Improve this report!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with testutils/testcluster.TestClusterStart and inspect the linked test report, captured logs, and test_server_shim.go comment. Reproduce the failure with the reported race, run, and shard parameters, then identify and fix the cause so TestClusterStart passes reliably.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.