Re: The innodb.innodb_bug60049 test fails in 5.5.11
It is bug of the purge_thread.
It seems to be that there are some records not-purged after shutdown, even if with inondb_fast_shutdown=0.

And this problem is caused also for normal 5.5.11 with innodb_purge_threads=1

I will investigate and fix soon.

Re: The innodb.innodb_bug60049 test fails in 5.5.11
fixed at rev. 104 of 5.5.11/ directly

Re: The innodb.innodb_bug60049 test fails in 5.5.11
The symptoms of this bug have resurfaced again:
http://jenkins.percona.com/view/Percona%20Server%205.5/job/percona-server-5.5-trunk/BUILD_TYPE=release,Host=centos6-64/74/testReport/junit/%28root%29/innodb/innodb_bug60049/

Comment:

Logfile:
CURRENT_TEST: innodb.innodb_bug60049
— /home/jenkins/workspace/percona-server-5.5-trunk/BUILD_TYPE/release/Host/centos6-64/Percona-Server-5.5.17-rel21.0/mysql-test/suite/innodb/r/innodb_bug60049.result 2011-10-12 15:10:25.000000000 +0300
+++ /home/jenkins/workspace/percona-server-5.5-trunk/BUILD_TYPE/release/Host/centos6-64/Percona-Server-5.5.17-rel21.0/mysql-test/suite/innodb/r/innodb_bug60049.reject 2011-11-17 15:15:06.528222320 +0300
@@ -5,4 +5,4 @@
@@innodb_fast_shutdown
0
Last record of ID_IND root page (9):
-1808000018050074000000000000000c5359535f464f524549474e5f434f4c53
+18080000180500d6000000000000000c5359535f464f524549474e5f434f4c53

mysqltest: Result content mismatch

Re: The innodb.innodb_bug60049 test fails in 5.5.11
Also seen in MariaDB 5.5 (with XtraDB). It is not repeatable on all hosts and/or build-options though

Re: The innodb.innodb_bug60049 test fails in 5.5.11
Can we still repeat this anywhere? I'm not seeing it in our recent jenkins builds.

Launchpad bug id: 756387