Percona Server moved to https://jira.percona.com/projects/PS

  1. Bug #756387
  2. Comment #3

Comment 3 for bug 756387

Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote : 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