cockroachdb / cockroachdb/cockroach
release-26.4: roachtest: replicagc-changed-peers/restart=false failed
Open
Nobody has claimed this yet.
branch-release-26.4
C-test-failure
O-roachtest
O-robot
release-blocker
T-kv
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
roachtest.replicagc-changed-peers/restart=false failed with artifacts on release-26.4 @ b4884d371d74d172ab184bc4ef0924ccb758f3c2:
Failed with:
(replicagc.go:337).waitForZeroReplicasOnN3: pq: could not determine data type of placeholder $1
test artifacts and logs in: /artifacts/replicagc-changed-peers/restart=false/run_1
Cluster Node to Ip Mapping:
| Node | Public IP | Private IP |
|---|---|---|
| teamcity-21524579-1789881036-75-n6cpu4-0001 | 10.91.99.105 | |
| teamcity-21524579-1789881036-75-n6cpu4-0002 | 10.91.101.183 | |
| teamcity-21524579-1789881036-75-n6cpu4-0003 | 10.91.101.185 | |
| teamcity-21524579-1789881036-75-n6cpu4-0004 | 10.91.101.184 | |
| teamcity-21524579-1789881036-75-n6cpu4-0005 | 10.91.97.85 | |
| teamcity-21524579-1789881036-75-n6cpu4-0006 | 10.91.96.106 |
Parameters:
arch=amd64cloud=gcecoverageBuild=falsecpu=4diskCount=0encrypted=falsefs=ext4localSSD=truemetamorphicDRPC=truemetamorphicLeases=leaderruntimeAssertionsBuild=false
Same failure on other branches
- #175681 roachtest: replicagc-changed-peers/restart=false failed [C-test-failure O-roachtest O-robot T-kv branch-master release-blocker]
- #171810 release-26.3: roachtest: replicagc-changed-peers/restart=false failed [A-testing B-runtime-assertions-enabled C-bug C-test-failure O-roachtest O-robot P-3 T-kv branch-release-26.3]
Jira issue: CRDB-68574
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 replicagc.go at line 337 and inspect the failing waitForZeroReplicasOnN3 call, then review the linked TeamCity log and artifacts for replicagc-changed-peers/restart=false. Compare the same failure on the linked branches and verify that the roachtest completes without the placeholder data-type error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases, distributed-systems, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100