Suppress a safemutex warning pending fix of MBug#578117.

This commit is contained in:
unknown 2010-05-10 09:29:30 +02:00
parent 50ddf3c111
commit 4402f65267
2 changed files with 6 additions and 0 deletions

View file

@ -1,4 +1,5 @@
drop table if exists t1, t2; drop table if exists t1, t2;
CALL mtr.add_suppression("Found wrong usage of mutex 'LOCK_sync' and 'LOCK_active'");
CREATE TABLE t1 (a INT PRIMARY KEY) ENGINE=innodb; CREATE TABLE t1 (a INT PRIMARY KEY) ENGINE=innodb;
CREATE TABLE t2 (b INT PRIMARY KEY) ENGINE=pbxt; CREATE TABLE t2 (b INT PRIMARY KEY) ENGINE=pbxt;
BEGIN; BEGIN;

View file

@ -4,6 +4,11 @@
drop table if exists t1, t2; drop table if exists t1, t2;
--enable_warnings --enable_warnings
# This warning is indication of a real bug, MBug#578117.
# But it is not a regression, so we suppress it to get a clean test run.
# This suppression must be removed as part of MBug#578117 fix.
CALL mtr.add_suppression("Found wrong usage of mutex 'LOCK_sync' and 'LOCK_active'");
# #
# bug lp:544173, xa crash with two 2pc-capable storage engines without binlog # bug lp:544173, xa crash with two 2pc-capable storage engines without binlog
# #