diff options
| author | Luis Soares <luis.soares@oracle.com> | 2010-11-27 11:51:07 +0000 |
|---|---|---|
| committer | Luis Soares <luis.soares@oracle.com> | 2010-11-27 11:51:07 +0000 |
| commit | 6ce0bd8aff9c26fa9eaeee421b1cfaa9ac38e6ae (patch) | |
| tree | 7c4ec96c1a9339f1fffd1180fdb3d34d7709bd25 /mysql-test/extra | |
| parent | d6d0827ec6d79326ef8443a40f06a4962af6a36f (diff) | |
| download | mariadb-git-6ce0bd8aff9c26fa9eaeee421b1cfaa9ac38e6ae.tar.gz | |
BUG#58416: binlog.binlog_row_failure_mixing_engines fails on
win x86 debug_max
The windows MTR run exhibited a different test execution
ordering (due to the fact that in these platforms MTR is invoked
with --parallel > 1). This uncovered a bug in the aforementioned
test case, which is triggered by the following conditions:
1. server is not restarted between two different tests;
2. the test before binlog.binlog_row_failure_mixing_engines
issues flush logs;
3. binlog.binlog_row_failure_mixing_engines uses binlog
positions to limit the output of show_binlog_events;
4. binlog.binlog_row_failure_mixing_engines does not state which
binlog file to use, thence it uses a wrong binlog file with
the correct position.
There are two possible fixes: 1. make sure that the test start
from a clean slate - binlog wise; 2. in addition to the position,
also state the binary log file before sourcing
show_binlog_events.inc .
We go for fix #1, ie, deploy a RESET MASTER before the test is
actually started.
Diffstat (limited to 'mysql-test/extra')
| -rw-r--r-- | mysql-test/extra/binlog_tests/binlog_failure_mixing_engines.test | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/mysql-test/extra/binlog_tests/binlog_failure_mixing_engines.test b/mysql-test/extra/binlog_tests/binlog_failure_mixing_engines.test index 54f3c538c79..d537e29c1a8 100644 --- a/mysql-test/extra/binlog_tests/binlog_failure_mixing_engines.test +++ b/mysql-test/extra/binlog_tests/binlog_failure_mixing_engines.test @@ -60,6 +60,7 @@ # Please, remove this test case after pushing WL#2687. ################################################################################ +RESET MASTER; --echo ################################################################################### --echo # CONFIGURATION |