cockroachdb / cockroachdb/cockroach

roachtest: backup/minio failed

Open
#175,076 3 comments 0 reactions 0 assignees View on GitHub
branch-release-25.2.24-rc C-test-failure O-roachtest O-robot T-field-eng
Dominant language
Go
Stars
32.5k
Forks
4.1k
PR merge metrics
PR metrics pending

Description

roachtest.backup/minio [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_Roachtests_RoachtestNightlyGcePrivateBazel/21513626?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_Roachtests_RoachtestNightlyGcePrivateBazel/21513626?buildTab=artifacts#/backup/minio) on release-25.2.24-rc @ [92c7311721160180bed1228023264f6df947fc1e](https://github.com/cockroachdb/cockroach/commits/92c7311721160180bed1228023264f6df947fc1e):

```
(cluster.go:2562).Run: full command output in run_054119.363585634_n4_sudo-docker-run-name.log: COMMAND_PROBLEM: exit status 125
test artifacts and logs in: /artifacts/backup/minio/cpu_arch=arm64/run_1
```

Parameters:
- arch=arm64
- cloud=gce
- coverageBuild=false
- cpu=4
- diskCount=0
- encrypted=true
- fs=ext4
- localSSD=false
- metamorphicBufferedSender=false
- metamorphicLeases=default
- 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)

See: [Grafana](https://go.crdb.dev/roachtest-grafana/teamcity-21513626/backup-minio/1789191608667/1789191832997)

/cc @cockroachlabs/field-engineering

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

Contributor guide

Open the contributing guide

Research direction

Start with the roachtest README and the failure at cluster.go:2562, then inspect the linked TeamCity command output and artifacts under /artifacts/backup/minio/cpu_arch=arm64/run_1. Trace the exit status 125 for the backup/minio test using the listed GCE and Docker parameters. Done means the cause is fixed and the test passes with this configuration.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, gcp, go
Domain
testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.