Skip to content

Conversation

@mergify
Copy link

@mergify mergify bot commented Mar 8, 2025

  • amqp_client_SUITE: Use a dedicated CI job for this testsuite
  • amqp10_client: Handle close message in the open_sent state
  • amqp10_client: Fix crash in close_sent
  • amqp_client_SUITE: Retry connection in two testcases
  • amqp_client_SUITE: Ensure idle_time_out_on_server restores heartbeat value
  • amqp_client_SUITE: Use a dedicated AMQP-0-9-1 connection per testcase
  • amqp_client_SUITE: Close all connections in end_per_testcase/2
    This is an automatic backport of pull request amqp_client_SUITE: Fix frequent test failures #13409 done by Mergify.

dumbbell and others added 8 commits March 8, 2025 11:48
[Why]
This testsuite is very unstable and it is difficult to debug while it is
part of a `parallel-ct` group. It also forced us to re-run the entire
`parallel-ct` group just to retry that one testsuite.

(cherry picked from commit 2c66191)
[Why]
Without this, the connection process crashes. We see this happenning in
CI frequently.

(cherry picked from commit 77e3636)
Fix crash in close_sent since the client might receive the open frame if
it previously sent the close frame in state open_sent.

We explicitly ignore the open frame. The alternative is to add another
gen_statem state CLOSE_PIPE which  might be an overkill however.

This commit also fixes a wrong comment: No sessions have begun if the
app requests the connection to be closed in state open_sent.

(cherry picked from commit 6557686)
The testcases are `leader_transfer_credit` and
`dead_letter_into_stream`.

(cherry picked from commit 603ad0d)
…t value

[Why]
If the testcase fails, it was leaving the low heartbeat value in place,
leading to many subsequent tests to fail.

(cherry picked from commit 6084055)
... instead of a global one. Otherwise, one connection failure, even if
expected by a testcase, will affect all subsequent testcases negatively.

(cherry picked from commit ce5ba6d)
[Why]
Many tests do not clean up their connections if they encounter a
failure. This affects subsequent testcases negatively.

(cherry picked from commit 4d12efa)
(cherry picked from commit 0f9b693)
@mergify mergify bot added the make label Mar 8, 2025
@michaelklishin michaelklishin merged commit 1aa97a7 into v4.1.x Mar 8, 2025
273 checks passed
@michaelklishin michaelklishin deleted the mergify/bp/v4.1.x/pr-13409 branch March 8, 2025 12:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants