Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.11, 11.0, 11.1, 11.2, 11.4
-
None
Description
The test's header is not written to follow strictly the correct order of checks at test start.
Perhaps that was a reason of its some (though really rare) failure in BB.
It's easy to expose that by running mtr manually, like alone to only require
a binlog format that it does not like.
E.g
./mtr --mysqld=--binlog-format=row rpl.rpl_using_gtid_default
|
leads to
rpl.rpl_using_gtid_default 'row' [ fail ]
|
Test ended at 2024-04-29 18:51:42
|
 |
CURRENT_TEST: rpl.rpl_using_gtid_default
|
mysqltest: In included file "./include/rpl_init.inc":
|
included from ./include/master-slave.inc at line 39:
|
included from /home3/MDB/WTs/Review/A/mysql-test/suite/rpl/t/rpl_using_gtid_default.test at line 46:
|
At line 175: query 'SET GLOBAL gtid_slave_pos= ""' failed: ER_SLAVE_MUST_STOP (1198): This operation cannot be performed as you have a running slave ''; run STOP SLAVE '' first
|
|