cockroachdb / cockroachdb/cockroach

roachtest: cluster_creation failed

Open
#149,522 0 comments 0 reactions 0 assignees View on GitHub
branch-master 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/20101195?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_Roachtests_RoachtestNightlyIbmBazel/20101195?buildTab=artifacts#/ycsb/E/nodes=3/cpu=32/mvcc-range-keys=global) on master @ [255f60e14a03060b9b2ca81e38f7188c33173a7a](https://github.com/cockroachdb/cockroach/commits/255f60e14a03060b9b2ca81e38f7188c33173a7a):

```
test ycsb/E/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-52175

Contributor guide

Open the contributing guide

Research direction

Start with the TeamCity log and artifacts linked in the report, then read the roachtest README and the failure at test_runner.go:850. Reproduce the ycsb/E cluster_creation run with cloud=ibm and cpu=32, and trace why that CPU value is rejected. Done means the IBM roachtest configuration no longer reports an invalid CPU count and the run completes successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cloud, 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.