From 78cfa76f7edbe362c152d2ad4ad8e4012a61e437 Mon Sep 17 00:00:00 2001
From: Tomas Jelinek <tojeline@redhat.com>
Date: Wed, 17 Apr 2024 17:25:04 +0200
Subject: [PATCH] increase a timeout in a test

---
 pcs_test/tier0/daemon/app/test_app_remote.py | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/pcs_test/tier0/daemon/app/test_app_remote.py b/pcs_test/tier0/daemon/app/test_app_remote.py
index c6a6b235..dc176846 100644
--- a/pcs_test/tier0/daemon/app/test_app_remote.py
+++ b/pcs_test/tier0/daemon/app/test_app_remote.py
@@ -121,7 +121,10 @@ class SyncConfigMutualExclusive(AppTest):
         # Without lock the timeout should be enough to finish task. With the
         # lock it should raise because of timeout. The same timeout is used for
         # noticing differences between test with and test without lock.
-        return self.io_loop.run_sync(fetch_sync_options, timeout=0.5)
+        # The timeout needs to be long enough for the test to fit into it even
+        # if running on a slower machine. And it should be short enough not to
+        # make the test run unnecessary long.
+        return self.io_loop.run_sync(fetch_sync_options, timeout=2.5)
 
     def check_call_wrapper_without_lock(self, method):
         self.assert_wrappers_response(self.fetch_set_sync_options(method))
-- 
2.33.0

