From b3d29da3d2b0396fe1a4fe8aefb775d7dc6fe73f Mon Sep 17 00:00:00 2001 From: Johan Wikman Date: Tue, 8 May 2018 15:04:22 +0300 Subject: [PATCH] MXS-1861 Test that reveals problem As this is so closely related to MXS-1719 the test program for that is slightly modified to catch this one as well. --- maxscale-system-test/mxs1719.cpp | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/maxscale-system-test/mxs1719.cpp b/maxscale-system-test/mxs1719.cpp index b206a0cab..110a94bc0 100644 --- a/maxscale-system-test/mxs1719.cpp +++ b/maxscale-system-test/mxs1719.cpp @@ -44,6 +44,13 @@ void run(TestConnections& test) { // One multi-statement with two UPDATEs. test.try_query(pMysql, "UPDATE MXS_1719 SET a=1; UPDATE MXS_1719 SET a=1;"); + + // Sleep a while, so that the log is flushed. + sleep(5); + // This is actually related to MXS-1861 "masking filter logs warnings with + // multistatements" but it seems excessive to create a specific test for that. + test.log_excludes(0, "Received data, although expected nothing"); + // This will hang immediately, so we can shorten the timeout. test.set_timeout(5); test.try_query(pMysql, "SELECT * FROM MXS_1719");