Skip to content

Conversation

@dumbbell
Copy link
Collaborator

@dumbbell dumbbell commented Oct 2, 2025

Why

The *_queue_after_partition_recovery_1 testcases rely on the fact that the queue process retries to delete its queue record in its terminate function.

RabbitMQ 4.1.x and before don't have that. Thus, depending on the timing of the election of the Khepri leader after a network partition, the test might fail.

This is a follow-up commit to #14573.

…mixed-version testing

[Why]
The `*_queue_after_partition_recovery_1` testcases rely on the fact that
the queue process retries to delete its queue record in its terminate
function.

RabbitMQ 4.1.x and before don't have that. Thus, depending on the timing
of the election of the Khepri leader after a network partition, the test
might fail.
@dumbbell dumbbell added this to the 4.3.0 milestone Oct 2, 2025
@dumbbell dumbbell self-assigned this Oct 2, 2025
@dumbbell dumbbell marked this pull request as ready for review October 2, 2025 16:53
@dumbbell dumbbell merged commit 1d1faff into main Oct 2, 2025
568 of 569 checks passed
@dumbbell dumbbell deleted the fix-flaky-tests branch October 2, 2025 16:53
@dumbbell
Copy link
Collaborator Author

dumbbell commented Oct 2, 2025

This will be backported to 4.2.x as part of #14654.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants