diff options
| author | Jean-Sébastien Pédron <jean-sebastien@rabbitmq.com> | 2019-10-11 09:17:48 +0200 |
|---|---|---|
| committer | Jean-Sébastien Pédron <jean-sebastien@rabbitmq.com> | 2019-10-11 09:17:48 +0200 |
| commit | 152219052fd47a85c8bb4ab6e706915a31f72364 (patch) | |
| tree | 9f8c2ac2a1614c3b9d3bc7849ad2edd6d528c0c9 /test | |
| parent | 2cbbcdbb48b5b8b87bb19bc0e08669987dc9f5d0 (diff) | |
| download | rabbitmq-server-git-152219052fd47a85c8bb4ab6e706915a31f72364.tar.gz | |
quorum_queue_SUITE: Use rabbit_ct_broker_helpers:stop_node/2
... instead of `rabbitmqctl stop` in
`simple_confirm_availability_on_leader_change` testcase.
The problem with the latter is that it doesn't wait for the broker to
actually stop. Therefore we end up with an error when we try to restart
it after because the previous instance is still running.
Diffstat (limited to 'test')
| -rw-r--r-- | test/quorum_queue_SUITE.erl | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/test/quorum_queue_SUITE.erl b/test/quorum_queue_SUITE.erl index 384e7a818e..bed7dedae0 100644 --- a/test/quorum_queue_SUITE.erl +++ b/test/quorum_queue_SUITE.erl @@ -1197,7 +1197,7 @@ simple_confirm_availability_on_leader_change(Config) -> publish_confirm(Ch, QQ), %% stop the node hosting the leader - stop_node(Config, Node2), + ok = rabbit_ct_broker_helpers:stop_node(Config, Node2), %% this should not fail as the channel should detect the new leader and %% resend to that publish_confirm(Ch, QQ), |