cockroachdb / cockroachdb/cockroach

roachtest: cluster_creation failed

Open
#165,621 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/21244865?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_Roachtests_RoachtestNightlyIbmBazel/21244865?buildTab=artifacts#/kv0/enc=false/nodes=3/cpu=32/size=64kb/splt=100) on master @ [5dd5d5a09e7655742e7cb93329bf711c9b2603cb](https://github.com/cockroachdb/cockroach/commits/5dd5d5a09e7655742e7cb93329bf711c9b2603cb):

```
test kv0/enc=false/nodes=3/cpu=32/size=64kb/splt=100 failed: (test_runner.go:998).func4: invalid number of cpus 32 for IBM [owner=test-eng]
```

Parameters:
- cloud=ibm
- coverageBuild=false
- cpu=32
- diskCount=0
- runtimeAssertionsBuild=false
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-61480

Contributor guide

Open the contributing guide

Research direction

Start with the linked TeamCity log and the roachtest README, then inspect test_runner.go:998, where the invalid IBM CPU count is reported. Determine why cluster_creation requests 32 CPUs for IBM and verify the fix by rerunning the affected roachtest configuration until it passes.

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.