kv/kvserver: TestGossipHandlesReplacedNode failed

[cockroach-teamcity]

kv/kvserver.TestGossipHandlesReplacedNode failed on master @ c4ab095c4f65b9140661ed57adddc690b1e3ce3f:

=== RUN   TestGossipHandlesReplacedNode
    test_log_scope.go:170: test logs captured to: outputs.zip/logTestGossipHandlesReplacedNode3096570700
    test_log_scope.go:81: use -show-logs to present logs inline
    testcluster.go:687: timed out waiting for 4 store descriptors: map[1:{} 2:{} 3:{}]
    panic.go:626: -- test log scope end --
test logs left over in: outputs.zip/logTestGossipHandlesReplacedNode3096570700
--- FAIL: TestGossipHandlesReplacedNode (49.42s)

Parameters:

• attempt=1
• run=7
• shard=13

Help

See also: How To Investigate a Go Test Failure (internal)

Same failure on other branches

• kv/kvserver: TestGossipHandlesReplacedNode failed #121839 kv/kvserver: TestGossipHandlesReplacedNode failed [A-testing C-bug C-test-failure O-robot P-3 T-kv branch-release-23.1.18-rc]

/cc @cockroachdb/kv

This test on roachdash | Improve this report!

Jira issue: CRDB-38038

[miraradeva]

Duplicate of #121839.

[cockroach-teamcity]

kv/kvserver.TestGossipHandlesReplacedNode failed on master @ 021c72ae4a131bf511bff654fd3e4162947d3b15:

=== RUN   TestGossipHandlesReplacedNode
    test_log_scope.go:170: test logs captured to: outputs.zip/logTestGossipHandlesReplacedNode3524801508
    test_log_scope.go:81: use -show-logs to present logs inline
    testcluster.go:687: timed out waiting for 4 store descriptors: map[2:{} 3:{} 4:{}]
    panic.go:626: -- test log scope end --
test logs left over in: outputs.zip/logTestGossipHandlesReplacedNode3524801508
--- FAIL: TestGossipHandlesReplacedNode (88.26s)

Parameters:

• attempt=1
• race=true
• run=1
• shard=14

Help

See also: How To Investigate a Go Test Failure (internal)

Same failure on other branches

• kv/kvserver: TestGossipHandlesReplacedNode failed #123082 kv/kvserver: TestGossipHandlesReplacedNode failed [A-testing C-bug C-test-failure O-robot P-3 T-kv branch-release-24.1]

This test on roachdash | Improve this report!

[github-actions]

We have marked this test failure issue as stale because it has been
inactive for 1 month. If this failure is still relevant, removing the
stale label or adding a comment will keep it active. Otherwise,
we'll close it in 5 days to keep the test failure queue tidy.