cockroachdb / cockroachdb/cockroach

roachtest: cluster_creation failed

Open
#150,910 0 comments 0 reactions 0 assignees View on GitHub
branch-release-25.3 O-roachtest O-robot T-testeng X-infra-flake
Dominant language
Go
Stars
32.5k
Forks
4.1k
PR merge metrics
PR metrics pending

Description

roachtest.cluster_creation [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_Roachtests_RoachtestNightlyIbmBazel/20259200?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_Roachtests_RoachtestNightlyIbmBazel/20259200?buildTab=artifacts#/ycsb/D/nodes=3/cpu=32/mvcc-range-keys=global) on release-25.3 @ [360e1daefa78d51978d04a0059ec6337d66d1a31](https://github.com/cockroachdb/cockroach/commits/360e1daefa78d51978d04a0059ec6337d66d1a31):

```
test ycsb/D/nodes=3/cpu=32/mvcc-range-keys=global failed: (test_runner.go:850).func4: invalid number of cpus 32 for IBM [owner=test-eng]
```

Parameters:
- cloud=ibm
- coverageBuild=false
- cpu=32
- runtimeAssertionsBuild=false
- ssd=0
Help

See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)

See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)

/cc @cockroachdb/test-eng

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

Jira issue: CRDB-52992

Contributor guide

Open the contributing guide

Research direction

Start with pkg/cmd/roachtest/README.md and the failure location at test_runner.go:850, then reproduce the IBM run using the linked build artifacts and parameters. Determine which cluster_creation configuration or CPU validation is responsible, and verify the roachtest completes successfully with the expected IBM CPU settings.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.