Bug #97454 MTR tests failed for binlog.binlog_rewrite_order
Submitted: 1 Nov 2019 7:38 Modified: 11 Nov 2019 13:57
Reporter: jibin ge Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Tests Severity:S7 (Test Cases)
Version:8.0.18, 8.0.17, 8.0.16 OS:Any
Assigned to: CPU Architecture:Any
Tags: regression

[1 Nov 2019 7:38] jibin ge
Description:
./mysql-test-run binlog.binlog_rewrite_order
Logging: ./mysql-test-run  binlog.binlog_rewrite_order
MySQL Version 8.0.18
Checking supported features
 - Binaries are debug compiled
Using 'all' suites
Collecting tests
 - Adding combinations for binlog
Checking leftover processes
Removing old var directory
Creating var directory '/opt/test/simple/usr/local/mysql/mysql-test/var'
Installing system database
Using parallel: 1

==============================================================================
                  TEST NAME                       RESULT  TIME (ms) COMMENT
------------------------------------------------------------------------------
[ 33%] binlog.binlog_rewrite_order 'mix'         [ fail ]
        Test ended at 2019-11-01 12:03:26

MTR's internal check of the test case 'binlog.binlog_rewrite_order' 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: Results saved in '/opt/test/simple/usr/local/mysql/mysql-test/var/tmp/check-mysqld_1.result'.
mysqltest: Logging to '/opt/test/simple/usr/local/mysql/mysql-test/var/tmp/check-mysqld_1.log'.
mysqltest: Connecting to server localhost:13000 (socket /opt/test/simple/usr/local/mysql/mysql-test/var/tmp/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.
--- /opt/test/simple/usr/local/mysql/mysql-test/var/tmp/check-mysqld_1.result	2019-11-01 07:03:20.234366269 +0300
+++ /opt/test/simple/usr/local/mysql/mysql-test/var/tmp/check-mysqld_1.reject	2019-11-01 07:03:26.713916925 +0300
@@ -71,6 +71,15 @@
 #-------------- MYSQLTEST_VARDIR/run --------------
 mysqld.1.pid
 #-------------- MYSQLTEST_VARDIR/tmp --------------
+SQL_LOAD_MB-1-0
+SQL_LOAD_MB-1-1
+SQL_LOAD_MB-1-2
+SQL_LOAD_MB-2-0
+SQL_LOAD_MB-2-1
+SQL_LOAD_MB-2-2
+SQL_LOAD_MB-3-0
+SQL_LOAD_MB-3-1
+SQL_LOAD_MB-3-2
 mysqld.1
 #------------- MYSQLTEST_VARDIR/std_data ------------
 .mylogin.cnf

mysqltest: Result content mismatch

not ok
safe_process[2836]: Child process: 2837, exit: 1

How to repeat:

./mysql-test-run binlog.binlog_rewrite_order
[4 Nov 2019 5:15] MySQL Verification Team
Hello jibin ge,

Thank you for the report and feedback.
Verified as described with 8.0.18 Generic Linux(binary tarball build).

regards,
Umesh
[11 Nov 2019 13:57] Paul DuBois
Posted by developer:
 
Fixed in 8.0.19.

Work was done for test suite. No changelog entry required.