| Bug #46825 | rpl_commit_after_flush test fails on PB-2 | ||
|---|---|---|---|
| Submitted: | 20 Aug 2009 10:05 | Modified: | 5 Feb 2010 8:29 |
| Reporter: | Andrei Elkin | Email Updates: | |
| Status: | Can't repeat | Impact on me: | |
| Category: | Tests: Replication | Severity: | S3 (Non-critical) |
| Version: | 5.1 | OS: | Any |
| Assigned to: | Daogang Qu | CPU Architecture: | Any |
| Tags: | test failure | ||
[20 Aug 2009 10:05]
Andrei Elkin
[31 Aug 2009 11:07]
Andrei Elkin
More details on a fresher occurrence http://pb2.norway.sun.com/web.py?template=mysql_show_test_failure&test_failure_id=2286234 mysql-5.1-bugteam 498510 binary-max-sol10-sparc64-tar-gz 498651 takk-z5 test-max-sol10-sparc64 500100 tor04-z3 rpl_binlog_row rpl rpl_commit_after_flush None 2009-08-21 16:53:58 - Show/hide test output - Original output rpl.rpl_commit_after_flush w4 [ fail ] Found warnings/errors in server log file! Test ended at 2009-08-24 12:48:45 mysqltest: Logging to ''. mysqltest: Results saved in ''. mysqltest: Connecting to server localhost:13021 (socket /export/home/pb2/test/sb_0-704418-1251104712.26/tmp/Q1QoXUKHok/4/mysqld.2.sock) as 'root', connection 'default', attempt 0 ... mysqltest: ... Connected. mysqltest: Start processing test commands from './include/check-warnings.test' ... file_name line /export/home/pb2/test/sb_0-704418-1251104712.26/mysql-5.1.39-solaris10-sparc-test/mysql-test/var/4/log/mysqld.2.err 090824 13:47:58 InnoDB: Error: cannot allocate 139144 bytes of ^ Found warnings!! mysqltest: ... Done processing test commands. mysqltest: Test has succeeded! ok - saving '/export/home/pb2/test/sb_0-704418-1251104712.26/mysql-5.1.39-solaris10-sparc-test/mysql-test/var/4/log/rpl.rpl_commit_after_flush/' to '/export/home/pb2/test/sb_0-704418-1251104712.26/mysql-5.1.39-solaris10-sparc-test/mysql-test/var/log/rpl.rpl_commit_after_flush/' Retrying test, attempt(2/3)... rpl.rpl_row_log_innodb 'InnoDB plugin' w5 [ fail ] Test ended at 2009-08-24 12:48:45 CURRENT_TEST: rpl.rpl_row_log_innodb --- /export/home/pb2/test/sb_0-704418-1251104712.26/mysql-5.1.39-solaris10-sparc-test/mysql-test/suite/rpl/r/rpl_row_log_innodb.result 2009-08-21 18:44:18.000000000 +0300 +++ /export/home/pb2/test/sb_0-704418-1251104712.26/mysql-5.1.39-solaris10-sparc-test/mysql-test/suite/rpl/r/rpl_row_log_innodb.reject 2009-08-24 13:48:07.108226754 +0300 @@ -227,13 +227,13 @@ slave-bin.000001 # Query 1 # BEGIN slave-bin.000001 # Table_map 1 # table_id: # (test.t1) slave-bin.000001 # Write_rows 1 # table_id: # flags: STMT_END_F -slave-bin.000001 # Xid 1 # COMMIT /* XID */ +slave-bin.000001 # Query 1 # COMMIT slave-bin.000001 # Query 1 # use `test`; drop table t1 slave-bin.000001 # Query 1 # use `test`; create table t1 (word char(20) not null)ENGINE=InnoDB slave-bin.000001 # Query 1 # BEGIN slave-bin.000001 # Table_map 1 # table_id: # (test.t1) slave-bin.000001 # Write_rows 1 # table_id: # flags: STMT_END_F -slave-bin.000001 # Xid 1 # COMMIT /* XID */ +slave-bin.000001 # Query 1 # COMMIT slave-bin.000001 # Query 1 # use `test`; create table t3 (a int)ENGINE=InnoDB slave-bin.000001 # Rotate 2 # slave-bin.000002;pos=4 show binlog events in 'slave-bin.000002' from 4; @@ -243,7 +243,7 @@ slave-bin.000002 # Query 1 # BEGIN slave-bin.000002 # Table_map 1 # table_id: # (test.t2) slave-bin.000002 # Write_rows 1 # table_id: # flags: STMT_END_F -slave-bin.000002 # Xid 1 # COMMIT /* XID */ +slave-bin.000002 # Query 1 # COMMIT SHOW SLAVE STATUS; Slave_IO_State # Master_Host 127.0.0.1
[5 Feb 2010 3:22]
Daogang Qu
Hi Andrei, I'm going to set its status to 'Can't repeat' if you agree as the bug can't be reproduced. I have successfully run the 'rpl_commit_after_flush' test for two days on astra03.norway.sun.com, witch is a sol10 sparc64 platform host on PB2. And the failure info reported have not been appeared in recent three months on PB2.
