cockroachdb / cockroachdb/cockroach
roachtest: better cluster creation error reporting
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
At the moment if a cluster creation fails for any reason during a roachtest a github issue is created under the infrastructure flakes label.
Since these get mixed in with all the cluster creation failures including resource problems they often go unnoticed.
*Suggested solution*:
We should somehow determine when a cluster creation failure is not regarding a resource problem and make it more noticeable either via a slack post or not including the infra flake label in these cases.
Jira issue: CRDB-55655
Contributor guide
Research direction
Start in the roachtest cluster-creation failure handling and trace how failures receive the infrastructure flakes label and create GitHub issues. Done means resource-related failures remain classified as infrastructure flakes while other cluster-creation failures are distinguished and surfaced more noticeably, such as through Slack or a different label.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- infrastructure, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100