roachtest: replicagc-changed-peers/restart=false failed [racing snapshots during decommission] #156849
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=false failed with artifacts on release-24.3 @ 312bef74c778c17fb77228c22838fb3efd331562:
(replicagc.go:96).runReplicaGCChangedPeers: COMMAND_PROBLEM: exit status 1
test artifacts and logs in: /artifacts/replicagc-changed-peers/restart=false/run_1
Parameters:
arch=amd64cloud=gcecoverageBuild=falsecpu=4encrypted=falsefs=ext4localSSD=trueruntimeAssertionsBuild=truessd=0
This test on roachdash | Improve this report!
Jira issue: CRDB-56223
Metadata
Metadata
Assignees
Labels
Anything in KV that doesn't belong in a more specific category.Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.Broken test (automatically or manually discovered).Originated from a bot.Issues/test failures with no fix SLAKV TeamUsed to mark GA and release blockers, technical advisories, and bugs for 24.3