Bug #56498 rpl_test_framework fails in 5.1 in stmt mode
Submitted: 2 Sep 2010 13:44 Modified: 8 Sep 2010 15:55
Reporter: Sveta Smirnova Email Updates:
Status: Not a Bug Impact on me:
None 
Category:Tests: Replication Severity:S3 (Non-critical)
Version:5.1 OS:Any
Assigned to: CPU Architecture:Any

[2 Sep 2010 13:44] Sveta Smirnova
Description:
rpl_test_framework fails in 5.1 in stmt mode

How to repeat:
$./mtr rpl_test_framework
Logging: ./mtr  rpl_test_framework
100902 15:41:23 [Note] Plugin 'FEDERATED' is disabled.
100902 15:41:23 [Note] Plugin 'ndbcluster' is disabled.
MySQL Version 5.1.51
Checking supported features...
 - using ndbcluster when necessary, mysqld supports it
 - SSL connections supported
 - binaries are debug compiled
Collecting tests...
 - adding combinations for rpl
vardir: /users/ssmirnova/blade12/src/mysql-5.1/mysql-test/var
Checking leftover processes...
 - found old pid 10680 in 'mysqld.2.pid', killing it...
   process did not exist!
Removing old var directory...
 - WARNING: Using the 'mysql-test/var' symlink
Creating var directory '/users/ssmirnova/blade12/src/mysql-5.1/mysql-test/var'...
Installing system database...
Using server port 46191

==============================================================================

TEST                                      RESULT   TIME (ms)
------------------------------------------------------------

worker[1] Using MTR_BUILD_THREAD 300, with reserved ports 13000..13009
rpl.rpl_test_framework 'row'             [ skipped ]  Doesn't support --binlog-format='row'
rpl.rpl_test_framework 'mix'             [ skipped ]  Doesn't support --binlog-format='mixed'
rpl.rpl_test_framework 'stmt'            [ fail ]
        Test ended at 2010-09-02 15:41:25

CURRENT_TEST: rpl.rpl_test_framework
mysqltest: In included file "./include/rpl_init.inc": At line 75: Can't initialize replace from 'replace_result $SLAVE_MYPORT1 MASTER_C_PORT $_binlog_file MASTER_C_LOG_FILE'

The result from queries just before the failure was:
< snip >
RESET SLAVE;
RESET MASTER;
STOP SLAVE;
RESET SLAVE;
SET auto_increment_increment = 4;
SET auto_increment_offset = 1;
RESET MASTER;
RESET SLAVE;
CHANGE MASTER TO master_host='127.0.0.1',master_port=MASTER_A_PORT,master_user='root',MASTER_LOG_FILE='MASTER_A_LOG_FILE';
SET auto_increment_increment = 4;
SET auto_increment_offset = 2;
RESET MASTER;
STOP SLAVE;
RESET SLAVE;
CHANGE MASTER TO master_host='127.0.0.1',master_port=MASTER_B_PORT,master_user='root',MASTER_LOG_FILE='MASTER_B_LOG_FILE';
SET auto_increment_increment = 4;
SET auto_increment_offset = 3;
RESET MASTER;
STOP SLAVE;
RESET SLAVE;

More results from queries before failure can be found in /users/ssmirnova/blade12/src/mysql-5.1/mysql-test/var/log/rpl_test_framework.log
[2 Sep 2010 16:28] Sveta Smirnova
This is 5.1-main tree.
[3 Sep 2010 9:02] Luis Soares
I can't find traces of the test case in mysql-5.1 main tree. Details:

  tree: mysql-5.1
rev-id: build@mysql.com-20100819151858-muaaor6jojb5ouzj

[...]/clones/mysql-5.1$ bzr ls mysql-test/suite/rpl/t/ | grep rpl_test_
[...]/clones/mysql-5.1$ 

Perhaps Sveta tested this on a main tree with some patch (containing traces of rpl_test_framework) applied?
[6 Sep 2010 14:43] Sveta Smirnova
Hm...

Looks like my tree is really modified:

$bzr log mysql-test/suite/rpl/t/rpl_test_framework.test 
bzr: ERROR: Path unknown at end or start of revision range: mysql-test/suite/rpl/t/rpl_test_framework.test

Please close it as "Not a Bug" or as you think is appropriate.