cockroachdb / cockroachdb/cockroach

roachtest: cluster_creation failed

Open
#151,239 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/20281261?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_Roachtests_RoachtestNightlyIbmBazel/20281261?buildTab=artifacts#/ycsb/F/nodes=3/cpu=32/isolation-level=read-committed) on master @ [9831be5f895ec7758d43bbec0df76f1e14e78d44](https://github.com/cockroachdb/cockroach/commits/9831be5f895ec7758d43bbec0df76f1e14e78d44):

```
test ycsb/F/nodes=3/cpu=32/isolation-level=read-committed failed: (test_runner.go:872).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-53134

Contributor guide

Open the contributing guide

Research direction

Start with the roachtest README and the failure at test_runner.go:872, then inspect the cluster_creation run and its TeamCity artifacts for the IBM configuration using 32 CPUs. Done means the ycsb/F IBM run no longer fails with the invalid-CPU error, with the resulting behavior covered by the relevant roachtest validation.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cloud, testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.