MTR's internal check of the test case 'main.percona_slowlog_size_limits' failed.
This means that the test case does not preserve the state that existed
before the test case was executed. Most likely the test case did not
do a proper clean-up. It could also be caused by the previous test run
by this thread, if the server wasn't restarted.
This is the diff of the states of the servers before and after the
test case was executed:
mysqltest: Logging to '/Users/laurynas/percona/obj-percona-5.5-release-openssl/mysql-test/var/5/tmp/check-mysqld_1.log'.
mysqltest: Results saved in '/Users/laurynas/percona/obj-percona-5.5-release-openssl/mysql-test/var/5/tmp/check-mysqld_1.result'.
mysqltest: Connecting to server localhost:13041 (socket /Users/laurynas/percona/obj-percona-5.5-release-openssl/mysql-test/var/tmp/5/mysqld.1.sock) as 'root', connection 'default', attempt 0 ...
mysqltest: ... Connected.
mysqltest: Start processing test commands from './include/check-testcase.test' ...
mysqltest: ... Done processing test commands.
--- /Users/laurynas/percona/obj-percona-5.5-release-openssl/mysql-test/var/5/tmp/check-mysqld_1.result 2017-08-17 11:04:53.000000000 +0300
+++ /Users/laurynas/percona/obj-percona-5.5-release-openssl/mysql-test/var/5/tmp/check-mysqld_1.reject 2017-08-17 11:04:58.000000000 +0300
@@ -42,13 +42,22 @@
mysqld.1
mysqld.1.sock
$MYSQLTEST_VARDIR:
-abcd.000001
+abcd.000063
+abcd.000064
+abcd.000065
+abcd.000066
+abcd.000067
log
my.cnf
mysqld.1
run
std_data
tmp
+zxcv.000063
+zxcv.000064
+zxcv.000065
+zxcv.000066
+zxcv.000067
VARIABLE_NAME VARIABLE_VALUE
AUTOCOMMIT ON
AUTOMATIC_SP_PRIVILEGES ON
main.percona_ slowlog_ size_limits w5 [ pass ] 3749
MTR's internal check of the test case 'main.percona_ slowlog_ size_limits' failed. laurynas/ percona/ obj-percona- 5.5-release- openssl/ mysql-test/ var/5/tmp/ check-mysqld_ 1.log'. laurynas/ percona/ obj-percona- 5.5-release- openssl/ mysql-test/ var/5/tmp/ check-mysqld_ 1.result' . laurynas/ percona/ obj-percona- 5.5-release- openssl/ mysql-test/ var/tmp/ 5/mysqld. 1.sock) as 'root', connection 'default', attempt 0 ... check-testcase. test' ... laurynas/ percona/ obj-percona- 5.5-release- openssl/ mysql-test/ var/5/tmp/ check-mysqld_ 1.result 2017-08-17 11:04:53.000000000 +0300 laurynas/ percona/ obj-percona- 5.5-release- openssl/ mysql-test/ var/5/tmp/ check-mysqld_ 1.reject 2017-08-17 11:04:58.000000000 +0300 SP_PRIVILEGES ON
This means that the test case does not preserve the state that existed
before the test case was executed. Most likely the test case did not
do a proper clean-up. It could also be caused by the previous test run
by this thread, if the server wasn't restarted.
This is the diff of the states of the servers before and after the
test case was executed:
mysqltest: Logging to '/Users/
mysqltest: Results saved in '/Users/
mysqltest: Connecting to server localhost:13041 (socket /Users/
mysqltest: ... Connected.
mysqltest: Start processing test commands from './include/
mysqltest: ... Done processing test commands.
--- /Users/
+++ /Users/
@@ -42,13 +42,22 @@
mysqld.1
mysqld.1.sock
$MYSQLTEST_VARDIR:
-abcd.000001
+abcd.000063
+abcd.000064
+abcd.000065
+abcd.000066
+abcd.000067
log
my.cnf
mysqld.1
run
std_data
tmp
+zxcv.000063
+zxcv.000064
+zxcv.000065
+zxcv.000066
+zxcv.000067
VARIABLE_NAME VARIABLE_VALUE
AUTOCOMMIT ON
AUTOMATIC_
mysqltest: Result content mismatch