Bug #72937 main.max_statement_time fails with result mismatch, test contains race?
Submitted: 10 Jun 2014 14:06
Reporter: Sven Sandberg Email Updates:
Status: Verified Impact on me:
None 
Category:Tests: Server Severity:S3 (Non-critical)
Version:5.7 OS:Any
Assigned to: CPU Architecture:Any

[10 Jun 2014 14:06] Sven Sandberg
Description:
max_statement_time failed with result mismatch:

main.max_statement_time                  w7 [ fail ]
        Test ended at 2014-06-06 20:47:34

CURRENT_TEST: main.max_statement_time
--- E:/hudson_rpl/bzr/hudson/workspace/reviews-windows/sven_bug18751585_2_mysql-trunk.bundle.d/mysql-trunk/mysql-test/r/max_statement_time.result	2014-06-06 12:14:34.387000000 +0300
+++ R:\var-hudson-reviews-windows\7\log\max_statement_time.reject	2014-06-06 21:47:33.332610500 +0300
@@ -317,7 +317,7 @@
 SET @@SESSION.max_statement_time = 950;
 SELECT SLEEP(1);
 SLEEP(1)
-1
+0
 SET @@SESSION.max_statement_time = 1250;
 SELECT SLEEP(1);
 SLEEP(1)

mysqltest: Result content mismatch

How to repeat:
http://fimafeng11.no.oracle.com:8080/job/reviews-windows/1967/consoleText

Suggested fix:
Guessing that the test contains a race. Suggest to replace 950 by something much smaller and 1250 with something much bigger to reduce the risk that this happens again.
[18 Feb 2021 9:57] Erlend Dahl
Bug#77959 max_statement_time test is unstable

was marked as a duplicate.