Reduce excessive sleeping in tests

Some of the tests waited for excessively long periods of time for changes
to propagate. With a one second monitor interval, a sleep of around five
seconds should be plenty enough for all monitor related changes to be
propagated to all systems.
This commit is contained in:
Markus Mäkelä
2017-12-20 10:44:14 +02:00
parent 9962191722
commit b54dca50b5
5 changed files with 17 additions and 86 deletions

View File

@ -35,7 +35,7 @@ int main(int argc, char *argv[])
}
Test->set_timeout(30);
sleep(15);
sleep(5);
Test->set_timeout(30);
Test->tprintf("Connecting to all MaxScale services, expecting error\n");
@ -57,7 +57,6 @@ int main(int argc, char *argv[])
Test->repl->unblock_all_nodes();
Test->stop_timeout();
sleep(15);
Test->check_log_err(0, "fatal signal 11", false);
Test->check_log_err(0, "Failed to create new router session for service", true);