-
Notifications
You must be signed in to change notification settings - Fork 4k
amqp_client_SUITE: Fix frequent test failures (backport #13409) #13475
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
[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) # Conflicts: # deps/rabbit/Makefile
[Why] Without this, the connection process crashes. We see this happenning in CI frequently. (cherry picked from commit 77e3636) # Conflicts: # deps/amqp10_client/src/amqp10_client_connection.erl
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) # Conflicts: # deps/amqp10_client/src/amqp10_client_connection.erl
The testcases are `leader_transfer_credit` and `dead_letter_into_stream`. (cherry picked from commit 603ad0d) # Conflicts: # deps/rabbit/test/amqp_client_SUITE.erl
…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) # Conflicts: # deps/rabbit/test/amqp_client_SUITE.erl
... 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) # Conflicts: # deps/rabbit/test/amqp_client_SUITE.erl
[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)
|
Cherry-pick of 2c66191 has failed: Cherry-pick of 77e3636 has failed: Cherry-pick of 6557686 has failed: Cherry-pick of 603ad0d has failed: Cherry-pick of 6084055 has failed: Cherry-pick of ce5ba6d has failed: To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally |
closemessage in theopen_sentstateidle_time_out_on_serverrestores heartbeat valueend_per_testcase/2This is an automatic backport of pull request amqp_client_SUITE: Fix frequent test failures #13409 done by Mergify.