[MDEV-3753] LP:756387 - The innodb.innodb_bug60049 test fails in 5.5.11 Created: 2011-12-02  Updated: 2014-06-20  Resolved: 2012-10-04

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Alexey Kopytov Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: Launchpad

Attachments: XML File LPexportBug756387.xml    

 Description   

5.5.11 contains a new test, innodb.innodb_bug60049. The test passes in the upstream server, but fails in lp:percona-server/5.5.11 as follows on both Linux and Mac OS X:

CURRENT_TEST: innodb.innodb_bug60049
— /mnt/data/home/alexey.kopytov/src/percona/5.5.11/Percona-Server/mysql-test/suite/innodb/r/innodb_bug60049.result 2011-03-31 16:36:17.000000000 +0300
+++ /mnt/data/home/alexey.kopytov/src/percona/5.5.11/Percona-Server/mysql-test/suite/innodb/r/innodb_bug60049.reject 2011-04-10 12:11:00.000000000 +0300
@@ -5,4 +5,4 @@
@@innodb_fast_shutdown
0
Last record of ID_IND root page (9):
-1808000018050074000000000000000c5359535f464f524549474e5f434f4c53
+18080000180500c0000000000000000c5359535f464f524549474e5f434f4c53

mysqltest: Result content mismatch

 Comments   
Comment by Rasmus Johansson (Inactive) [ 2011-04-11 ]

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.

Comment by Rasmus Johansson (Inactive) [ 2011-04-12 ]

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

Comment by Laurynas Biveinis [ 2011-11-21 ]

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

Comment by Kristian Nielsen [ 2011-12-02 ]

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

Comment by Stewart Smith [ 2012-09-25 ]

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.

Comment by Rasmus Johansson (Inactive) [ 2012-09-25 ]

Launchpad bug id: 756387

Generated at Thu Feb 08 06:50:57 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.