raft: failure in src/v/raft/tests/jitter_tests.cc

[NyaliaLui]

Seen in two seperate PRs
https://buildkite.com/redpanda/redpanda/builds/9635#93b73389-5076-4d23-b12e-7eba3b98a460/6-5137

https://buildkite.com/redpanda/redpanda/builds/9631#d203e405-bcec-427f-a98a-e7e906604f4f/6-5140

[NyaliaLui]

Seen again in https://buildkite.com/redpanda/redpanda/builds/12398#0181ee90-d110-4bb4-b315-10938fc6f14c

[ztlpn]

These are different failures:

https://buildkite.com/redpanda/redpanda/builds/9635#93b73389-5076-4d23-b12e-7eba3b98a460/6-5137
and
https://buildkite.com/redpanda/redpanda/builds/9631#d203e405-bcec-427f-a98a-e7e906604f4f/6-5140

are

../../../src/v/raft/tests/append_entries_test.cc(764): �[4;31;49mfatal error: in "test_linarizable_barrier_leader_ack": critical check leader_raft->committed_offset() == leader_raft->dirty_offset() has failed [{-9223372036854775808} != {112}]�[0;39;49m

and https://buildkite.com/redpanda/redpanda/builds/12398#0181ee90-d110-4bb4-b315-10938fc6f14c

is

../../../src/v/raft/tests/raft_group_fixture.h(574): �[4;31;49mfatal error: in "replace_whole_group": Timeout elapsed while wating for: new nodes are up to date�[0;39;49m

(duplicate of #342)

Confusion arises because any error in test_raft_rpunit generates the following message:

*** 1 failure is detected in the test module "../../../src/v/raft/tests/jitter_tests.cc"

[ztlpn]

And looks like the original test_linarizable_barrier_leader_ack issue is a duplicate of #4518 that was fixed in #4555 so we can close this one 🎉