Said tests fails in 5.1.55 revision 198:
main.percona_slow_extended-slave_innodb_stats [ fail ]
Test ended at 2011-02-24 21:10:46
CURRENT_TEST: main.percona_slow_extended-slave_innodb_stats
--- /var/lib/buildbot/slaves/percona-server-51-12/DEB_Ubuntu_lucid_amd64/work/percona-server-5.1.55-12.6-199.lucid/mysql-test/r/percona_slow_extended-slave_innodb_stats.result 2011-02-24 23:37:04.000000000 +0300
+++ /var/lib/buildbot/slaves/percona-server-51-12/DEB_Ubuntu_lucid_amd64/work/percona-server-5.1.55-12.6-199.lucid/mysql-test/r/percona_slow_extended-slave_innodb_stats.reject 2011-02-25 00:10:46.000000000 +0300
@@ -1,9 +1,5 @@
-stop slave;
-drop table if exists t1,t2,t3,t4,t5,t6,t7,t8,t9;
-reset master;
-reset slave;
-drop table if exists t1,t2,t3,t4,t5,t6,t7,t8,t9;
-start slave;
+include/master-slave.inc
+[connection master]
DROP TABLE IF EXISTS t;
CREATE TABLE t(id INT,data CHAR(30)) ENGINE=InnoDB;
INSERT INTO t VALUES
@@ -15,7 +11,9 @@
INSERT INTO t SELECT t2.id,t2.data from t as t1, t as t2;
INSERT INTO t SELECT t2.id,t2.data from t as t1, t as t2;
STOP SLAVE;
+include/wait_for_slave_to_stop.inc
START SLAVE;
+include/wait_for_slave_to_start.inc
INSERT INTO t SELECT t.id,t.data from t;
DROP TABLE IF EXISTS t;
FLUSH LOGS;
mysqltest: Result content mismatch
Tested in lucid 64bits
Found this problem when compiling 5.1.56 in CentOS:
main.percona_ slow_extended- slave_innodb_ stats [ pass ] 4260
MTR's internal check of the test case 'main.percona_ slow_extended- slave_innodb_ stats' failed. ignacio. nin/src/ work/BUILD/ Percona- Server- 5.1.56/ mysql-test/ var/tmp/ check-mysqld_ 2.log'. ignacio. nin/src/ work/BUILD/ Percona- Server- 5.1.56/ mysql-test/ var/tmp/ check-mysqld_ 2.result' . nin/src/ work/BUILD/ Percona- Server- 5.1.56/ mysql-test/ var/tmp/ mysqld. 2.sock) as 'root', connection 'default', attempt 0 check-testcase. test' ... nin/src/ work/BUILD/ Percona- Server- 5.1.56/ mysql-test/ var/tmp/ check-mysqld_ 2.result 2011-04-13 01:41:39.042285782 +0300 nin/src/ work/BUILD/ Percona- Server- 5.1.56/ mysql-test/ var/tmp/ check-mysqld_ 2.reject 2011-04-13 01:41:43.605535326 +0300 Master_ Log_File # Ignore_ DB Behind_ Master NULL Behind_ Master 0 SSL_Verify_ Server_ Cert No
This means that the test case does not preserve the state that existed
before the test case was executed. Most likely the test case did not
do a proper clean-up. It could also be caused by the previous test run
by this thread, if the server wasn't restarted.
This is the diff of the states of the servers before and after the
test case was executed:
mysqltest: Logging to '/home/
mysqltest: Results saved in '/home/
mysqltest: Connecting to server localhost:13011 (socket /home/ignacio.
...
mysqltest: ... Connected.
mysqltest: Start processing test commands from './include/
mysqltest: ... Done processing test commands.
--- /home/ignacio.
+++ /home/ignacio.
@@ -1,4 +1,4 @@
-Slave_IO_State
+Slave_IO_State Waiting for master to send event
Master_Host 127.0.0.1
Master_User root
Master_Port 13010
@@ -8,8 +8,8 @@
Relay_Log_File #
Relay_Log_Pos #
Relay_
-Slave_IO_Running No
-Slave_SQL_Running No
+Slave_IO_Running Yes
+Slave_SQL_Running Yes
Replicate_Do_DB
Replicate_
Replicate_Do_Table
@@ -30,7 +30,7 @@
Master_SSL_Cert
Master_SSL_Cipher
Master_SSL_Key
-Seconds_
+Seconds_
Master_
Last_IO_Errno 0
Last_IO_Error
mysqltest: Result content mismatch
not ok
$ uname -a office. percona. com 2.6.32- 71.el6. x86_64 #1 SMP Wed Sep 1 01:33:01 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
Linux offbuild3.