kv/kvnemesis: TestKVNemesisSingleNode_ReproposalChaos failed

[cockroach-teamcity]

kv/kvnemesis.TestKVNemesisSingleNode_ReproposalChaos failed on master @ 3c837c2a86165188a26e8629b7e21b7ae0fb56ae:

Fatal error:

panic: test timed out after 4m57s
running tests:
	TestKVNemesisSingleNode_ReproposalChaos (4m45s)

Stack:

goroutine 70283 [running]:
testing.(*M).startAlarm.func1()
	GOROOT/src/testing/testing.go:2259 +0x3b9
created by time.goFunc
	GOROOT/src/time/sleep.go:176 +0x2d

Log preceding fatal error

=== RUN   TestKVNemesisSingleNode_ReproposalChaos
    test_log_scope.go:170: test logs captured to: outputs.zip/logTestKVNemesisSingleNode_ReproposalChaos1383871993
    test_log_scope.go:81: use -show-logs to present logs inline
    kvnemesis_test.go:327: seed: 5502448960364926010
    kvnemesis_test.go:234: kvnemesis logging to /var/lib/engflow/worker/work/3/exec/_tmp/97e4cd339b299bf4e67e2cedc7c6a7fe/kvnemesis2910829314

Parameters:

• attempt=1
• run=2
• shard=1

Help

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

Same failure on other branches

• kv/kvnemesis: TestKVNemesisSingleNode_ReproposalChaos failed #115598 kv/kvnemesis: TestKVNemesisSingleNode_ReproposalChaos failed [A-kv-transactions C-bug C-test-failure O-robot P-1 T-kv branch-release-23.2]

/cc @cockroachdb/kv

This test on roachdash | Improve this report!

Jira issue: CRDB-35457

[miraradeva]

The stack trace looks similar to #118005: waiting in the lock table for 4 minutes.

[arulajmani]

Closing as duplicate of #118005.