MySQL Bugs: #69458: rpl.rpl_deadlock_innodb test failing in 5.5.32

Bug #69458	rpl.rpl_deadlock_innodb test failing in 5.5.32
Submitted:	13 Jun 2013 9:19	Modified:	26 Nov 2013 9:04
Reporter:	Honza Horak (OCA)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Tests: Replication	Severity:	S3 (Non-critical)
Version:	5.5.32	OS:	Linux
Assigned to:		CPU Architecture:	Any

Description:
Running rpl.rpl_deadlock_innodb test case alone with "mysql-test-run --do-test=rpl_deadlock_innodb" works fine (test passes). However, when running that test together with other test cases with "mysql-test-run --do-test=rpl", I get error on x86_64 arch:

        Test ended at 2013-06-12 19:29:43
line
130612 20:28:58  InnoDB: Error: table `mysqld.2`.`#sql6acb_e8_1` does not exist in the InnoDB internal
130612 20:28:58  InnoDB: Error: table `mysqld.2`.`#sql6acb_5e_1` does not exist in the InnoDB internal
^ Found warnings in /home/hhorak/fedora/community-mysql/mysql-5.5.32/mysql-test/var/log/mysqld.2.err
ok

Since the same test did pass with 5.5.31, I tried the same test-suite (I simply copied mysql-test directory from 5.5.32 and run it with 5.5.31) and it passed. So, this tells me that the issue is not in the test suite but in the code itself.

How to repeat:
mysql-test-run --do-test=rpl

After digging a bit more into it I see many suppression of this kind of error in several test cases:

mysql-5.5.32/mysql-test/lib/v1/mtr_report.pl:                /InnoDB: Error: table `test`.`bug29807` does not exist in the InnoDB internal/ or
mysql-5.5.32/mysql-test/lib/v1/mtr_report.pl:                /InnoDB: Error: table `test`.`t[12]` does not exist in the InnoDB internal/ or
mysql-5.5.32/mysql-test/suite/parts/t/partition_debug_innodb.test:call mtr.add_suppression("InnoDB: Error: table .* does not exist in the InnoDB internal");
mysql-5.5.32/mysql-test/suite/parts/r/partition_debug_innodb.result:call mtr.add_suppression("InnoDB: Error: table .* does not exist in the InnoDB internal");
mysql-5.5.32/mysql-test/include/mix1.inc:call mtr.add_suppression("InnoDB: Error: table .test...bug29807. does not exist in the InnoDB internal");
mysql-5.5.32/mysql-test/include/mtr_warnings.sql: ("InnoDB: Error: table `test`.`t[123]` does not exist in the InnoDB internal"),

So is that something expected and we should only suppress that warning?

Hello Honza,

Thank you for the report.
Verified as described.

Thanks,
Umesh

A fix for this was pushed in 5.5.35, 5.6.16, 5.7.3. 

Please open a new bug if a similar issue occurs.