Bug #40101 | Result missmatch for rpl.rpl_events test | ||
---|---|---|---|
Submitted: | 17 Oct 2008 9:20 | Modified: | 17 Sep 2009 2:03 |
Reporter: | Rafal Somla | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | Tests: Replication | Severity: | S7 (Test Cases) |
Version: | 6.0, 5.1 | OS: | Any |
Assigned to: | Daogang Qu | CPU Architecture: | Any |
[17 Oct 2008 9:20]
Rafal Somla
[17 Oct 2008 10:50]
Sven Sandberg
There are actually several failure types in the xref link above. The one reported above has happened 4 times so far according to xref: http://tinyurl.com/6kz252 E.g., here: https://intranet.mysql.com/secure/pushbuild/showpush.pl?dir=bzr_mysql-6.0-backup-merge&ord... sapsrv2/n_mix ==== Failure 2 ==== rpl.rpl_events 'stmt' [ fail ] --- /data0/pushbuild/pb1/pb/bzr_mysql-maria/67/mysql-5.1.25-maria-alpha-pb67/mysql-test/suite/rpl/r/rpl_events.result 2008-10-08 12:46:05.000000000 +0300 +++ /data0/pushbuild/pb1/pb/bzr_mysql-maria/67/mysql-5.1.25-maria-alpha-pb67/mysql-test/suite/rpl/r/rpl_events.reject 2008-10-09 07:53:31.200340819 +0300 @@ -122,13 +122,15 @@ id c ts 1 manually TIMESTAMP 2 from justonce TIMESTAMP -affected rows: 2 +5 from alter er TIMESTAMP +affected rows: 3 "Checking event data on the slave" SELECT * FROM t1 ORDER BY id; id c ts 1 manually TIMESTAMP 2 from justonce TIMESTAMP -affected rows: 2 +5 from alter er TIMESTAMP +affected rows: 3 "Checking event is inactive on slave" SELECT db, name, status, originator FROM mysql.event WHERE db = 'test' AND name = 'justonce'; db name status originator mysqltest: Result content mismatch Stopping All Servers Restoring snapshot of databases ==== End failure 2 ==== Failure 2 is has failed over 400 times according to xref: http://tinyurl.com/6fqu8x E.g., here: https://intranet.mysql.com/secure/pushbuild/showpush.pl?dir=bzr_mysql-maria&order=67 debx86-b/n_stm
[17 Sep 2009 2:03]
Daogang Qu
The bug is fixed by a patch of bug#44331.