cockroachdb / cockroachdb/cockroach
release-26.2: roachtest: replicagc-changed-peers/restart=true failed
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
Note: This build has runtime assertions enabled. If the same failure was hit in a run without assertions enabled, there should be a similar failure without this message. If there isn't one, then this failure is likely due to an assertion violation or (assertion) timeout.
roachtest.replicagc-changed-peers/restart=true failed with artifacts on release-26.2 @ 27f9036eb1b1758c2ffc12fcc16565cccd180c16:
Failed with:
(replicagc.go:96).runReplicaGCChangedPeers: COMMAND_PROBLEM: exit status 1
test artifacts and logs in: /artifacts/replicagc-changed-peers/restart=true/cpu_arch=fips/run_1
Cluster Node to Ip Mapping:
| Node | Public IP | Private IP |
|---|---|---|
| teamcity-21523770-1789797356-205-n6cpu4-0001 | 10.91.96.82 | |
| teamcity-21523770-1789797356-205-n6cpu4-0002 | 10.91.98.33 | |
| teamcity-21523770-1789797356-205-n6cpu4-0003 | 10.91.98.156 | |
| teamcity-21523770-1789797356-205-n6cpu4-0004 | 10.91.96.33 | |
| teamcity-21523770-1789797356-205-n6cpu4-0005 | 10.91.97.102 | |
| teamcity-21523770-1789797356-205-n6cpu4-0006 | 10.91.98.109 |
Parameters:
arch=fipscloud=gcecoverageBuild=falsecpu=4diskCount=0encrypted=falsefs=ext4localSSD=truemetamorphicLeases=defaultmetamorphicWriteBuffering=trueruntimeAssertionsBuild=true
Same failure on other branches
- #175653 roachtest: replicagc-changed-peers/restart=true failed [C-test-failure O-roachtest O-robot T-kv branch-master release-blocker]
This test on roachdash | Improve this report!
Jira issue: CRDB-68561
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with pkg/cmd/roachtest/README.md and the failure at replicagc.go:96. Inspect the linked TeamCity artifacts and logs for replicagc-changed-peers/restart=true, then compare the same failure in issue #175653. Done means the cause is identified and the roachtest passes without reproducing this failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gcp, go
- Domain
- distributed-systems, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100