From e1f2b817340e50eea5492f694c42dadccfa8fc42 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Markus=20M=C3=A4kel=C3=A4?= <markus.makela@mariadb.com>
Date: Wed, 12 Sep 2018 14:23:57 +0300
Subject: [PATCH] Wait for monitor in bug547

The test expects the monitor to respond within 5 seconds. This is not
guaranteed to happen so waiting for a monitor interval instead of a
hard-coded duration provides for a more stable test.
---
 maxscale-system-test/bug547.cpp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/maxscale-system-test/bug547.cpp b/maxscale-system-test/bug547.cpp
index 3f301df31..c451ae090 100644
--- a/maxscale-system-test/bug547.cpp
+++ b/maxscale-system-test/bug547.cpp
@@ -35,7 +35,7 @@ int main(int argc, char *argv[])
     }
 
     Test->set_timeout(30);
-    sleep(5);
+    Test->maxscales->wait_for_monitor();
 
     Test->set_timeout(30);
     Test->tprintf("Connecting to all MaxScale services, expecting error\n");