roachtest: gossip/chaos/nodes=9 failed

[cockroach-teamcity]

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.gossip/chaos/nodes=9 failed with artifacts on release-24.3.3-rc @ 7dab2bb943152658ca94aeae83c450742ec361a5:

(gossip.go:78).2: gossip did not stabilize (dead node 9) in 36.5s
test artifacts and logs in: /artifacts/gossip/chaos/nodes=9/run_1

Parameters:

• arch=amd64
• cloud=gce
• coverageBuild=false
• cpu=4
• encrypted=false
• runtimeAssertionsBuild=true
• ssd=0

Help

See: roachtest README

See: How To Investigate (internal)

See: Grafana

Same failure on other branches

• roachtest: gossip/chaos/nodes=9 failed #136083 roachtest: gossip/chaos/nodes=9 failed [B-runtime-assertions-enabled C-bug C-test-failure O-roachtest O-robot P-3 T-kv X-duplicate branch-release-24.3.0-rc no-test-failure-activity]
• roachtest: gossip/chaos/nodes=9 failed #135154 roachtest: gossip/chaos/nodes=9 failed [A-testing C-bug C-test-failure O-roachtest O-robot P-3 T-kv branch-master]

/cc @cockroachdb/kv-triage

This test on roachdash | Improve this report!

Jira issue: CRDB-45886

[arulajmani]

From the logs:

2024/12/30 09:58:25 gossip.go:129: sleeping for 1s (0s)
2024/12/30 09:59:01 gossip.go:123: checking if gossip excludes dead node 9 (37s)

The symptoms here are similar to what we've been seeing in other failures for this test. We have #130737 open for it. I'll close this one out as a duplicate.