cockroachdb / cockroachdb/cockroach

basalt-26.3.2-rc-20260908: pkg/workload/fixture/fixture_test: TestImportFixtureNodeCount failed

Open
#175,578 1 comment 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

pkg/workload/fixture/fixture_test.TestImportFixtureNodeCount [failed](https://mesolite.cluster.engflow.com/invocations/default/6cda6f11-f948-43b1-8648-858357aa7fb3?testReportRun=1&testReportShard=1&testReportAttempt=1#targets-Ly9wa2cvd29ya2xvYWQvZml4dHVyZTpmaXh0dXJlX3Rlc3Q=) on basalt-26.3.2-rc-20260908 @ [807558e5e81666af257c811e925e4cae570abc28](https://github.com/cockroachdb/cockroach/commits/807558e5e81666af257c811e925e4cae570abc28):

```
=== RUN TestImportFixtureNodeCount
test_log_scope.go:172: test logs captured to: outputs.zip/logTestImportFixtureNodeCount1237831203
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=1
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:.*TestImportFixtureNodeCount.*&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 pkg/workload/fixture/fixture_test.go and TestImportFixtureNodeCount, then inspect the linked test report and captured logs for the node-count mismatch. Reproduce the failure with the reported race-enabled test configuration. Done means the underlying failure is identified and the test passes reliably.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
databases, testing-qa
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 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.