diff options
author | Philip Kuryloski <kuryloskip@vmware.com> | 2021-09-23 13:55:18 +0200 |
---|---|---|
committer | Philip Kuryloski <kuryloskip@vmware.com> | 2021-09-23 14:46:31 +0200 |
commit | ff62b722ddb778913b704e3047911ecaa1fb2132 (patch) | |
tree | 934d4bcc3f826902cde4c11cc177c00151d2c8b5 | |
parent | f0cf93841930b88a8171383f9dd7427fcee408df (diff) | |
download | rabbitmq-server-git-ff62b722ddb778913b704e3047911ecaa1fb2132.tar.gz |
Adjust the clustering_management_SUITE timeout at the ct level
Previously the bazel timeout and common test timeout were equal, which
meant that in practice the bazel timeout was often reached first, in
which case we don't receive the test logs
(cherry picked from commit 860653c97ae033c34240bbffd6ca86d6e4ba8d10)
-rw-r--r-- | deps/rabbit/test/clustering_management_SUITE.erl | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/deps/rabbit/test/clustering_management_SUITE.erl b/deps/rabbit/test/clustering_management_SUITE.erl index dafe590cac..2c7d0c1d67 100644 --- a/deps/rabbit/test/clustering_management_SUITE.erl +++ b/deps/rabbit/test/clustering_management_SUITE.erl @@ -65,7 +65,9 @@ groups() -> suite() -> [ %% If a test hangs, no need to wait for 30 minutes. - {timetrap, {minutes, 15}} + %% 14 minutes is one minute less than the current bazel timeout, + %% which should allow logs to be collected during a timeout + {timetrap, {minutes, 14}} ]. %% ------------------------------------------------------------------- |