summaryrefslogtreecommitdiff
path: root/test
diff options
context:
space:
mode:
authorPhilip Kuryloski <pkuryloski@pivotal.io>2020-04-29 16:28:57 +0200
committerPhilip Kuryloski <pkuryloski@pivotal.io>2020-04-29 16:28:57 +0200
commitd9ac4fba3cf82552da9c8bbedc74cfb9f2cfafda (patch)
tree5a2241fa485661fcc249a5576d2fd65d86fdebe4 /test
parentdc6e96543bd2f5c92396e09bf1df99d3c29fc63a (diff)
downloadrabbitmq-server-git-d9ac4fba3cf82552da9c8bbedc74cfb9f2cfafda.tar.gz
Use a 2 minute timeout when renaming nodes in cluster_rename_SUITE
This suite has been flaky, but it only fails with a timeout trap on the whole test. By setting a timeout for invidual rabbitmqctl commands, it should be easier to discern in a flake where things got stalled.
Diffstat (limited to 'test')
-rw-r--r--test/cluster_rename_SUITE.erl2
1 files changed, 1 insertions, 1 deletions
diff --git a/test/cluster_rename_SUITE.erl b/test/cluster_rename_SUITE.erl
index 93dccedcf1..772570faa6 100644
--- a/test/cluster_rename_SUITE.erl
+++ b/test/cluster_rename_SUITE.erl
@@ -266,7 +266,7 @@ do_rename_node(Config, Nodename, Map) ->
|| N <- Map
],
Ret = rabbit_ct_broker_helpers:rabbitmqctl(Config, Nodename,
- ["rename_cluster_node" | Map1]),
+ ["rename_cluster_node" | Map1], 120000),
case Ret of
{ok, _} ->
Config1 = update_config_after_rename(Config, Map1),