Bug #37712 rpl.rpl_locktrans_innodb fails sporadically on pushbuild
Submitted: 28 Jun 2008 10:19 Modified: 30 Jan 2009 17:11
Reporter: Sven Sandberg Email Updates:
Status: Closed Impact on me:
None 
Category:Tests: Replication Severity:S7 (Test Cases)
Version:6.0 OS:Any
Assigned to: Andrei Elkin CPU Architecture:Any
Tags: disabled, pushbuild, rpl_locktrans_innodb, sporadic, test failure
Triage: D3 (Medium)

[28 Jun 2008 10:19] Sven Sandberg
Description:
TEST: rpl.rpl_locktrans_innodb

Fails with the following message:

rpl.rpl_locktrans_innodb       [ fail ]

CURRENT_TEST: rpl.rpl_locktrans_innodb
--- /data0/pushbuild/pb/bzr_mysql-6.0-rpl/8/bzr_mysql-6.0-rpl-exp/mysql-test/suite/rpl/r/rpl_locktrans_innodb.result	2008-06-12 15:48:08.000000000 +0300
+++ /data0/pushbuild/pb/bzr_mysql-6.0-rpl/8/bzr_mysql-6.0-rpl-exp/mysql-test/suite/rpl/r/rpl_locktrans_innodb.reject	2008-06-13 17:44:48.000000000 +0300
@@ -100,12 +100,12 @@
 # Implicit lock method conversion due to mix in statement.
 LOCK TABLE t1 READ, t2 IN EXCLUSIVE MODE;
 Warnings:
-Warning	1613	Converted to non-transactional lock on 't2'
+Warning	1614	Converted to non-transactional lock on 't2'
 UNLOCK TABLES;
 # Lock t1 share (converted to read), t2 write.
 LOCK TABLE t1 IN SHARE MODE, t2 WRITE;
 Warnings:
-Warning	1613	Converted to non-transactional lock on 't1'
+Warning	1614	Converted to non-transactional lock on 't1'
 # Show t1 is read locked, t2 write locked.
 INSERT INTO t1 SELECT * FROM t2;
 ERROR HY000: Table 't1' was locked with a READ lock and can't be updated
@@ -116,8 +116,8 @@
 # Lock t1 exclusive (converted to write), t2 share (converted to read).
 LOCK TABLE t1 IN EXCLUSIVE MODE, t2 IN SHARE MODE;
 Warnings:
-Warning	1613	Converted to non-transactional lock on 't1'
-Warning	1613	Converted to non-transactional lock on 't2'
+Warning	1614	Converted to non-transactional lock on 't1'
+Warning	1614	Converted to non-transactional lock on 't2'
 # Show t1 is write locked, t2 read locked.
 INSERT INTO t1 SELECT * FROM t2;
 INSERT INTO t2 SELECT * FROM t1;
@@ -141,8 +141,8 @@
 ## Error is reported on first table only. Show both errors:
 SHOW WARNINGS;
 Level	Code	Message
-Error	1614	Cannot convert to non-transactional lock in strict mode on 't1'
-Error	1614	Cannot convert to non-transactional lock in strict mode on 't2'
+Error	1615	Cannot convert to non-transactional lock in strict mode on 't1'
+Error	1615	Cannot convert to non-transactional lock in strict mode on 't2'
 UNLOCK TABLES;
 SET @@SQL_MODE= @wl3561_save_sql_mode;
 #
@@ -162,7 +162,7 @@
 # Request a transactional lock, which is converted to non-transactional.
 LOCK TABLE t4 IN SHARE MODE;
 Warnings:
-Warning	1613	Converted to non-transactional lock on 't4'
+Warning	1614	Converted to non-transactional lock on 't4'
 # Try a conflict with the existing non-transactional lock.
 INSERT INTO t4 VALUES(444);
 ERROR HY000: Table 't4' was locked with a READ lock and can't be updated
@@ -179,8 +179,8 @@
 # Request a share lock on the view, which is converted to read locks.
 LOCK TABLE v1 IN SHARE MODE;
 Warnings:
-Warning	1613	Converted to non-transactional lock on 't3'
-Warning	1613	Converted to non-transactional lock on 't4'
+Warning	1614	Converted to non-transactional lock on 't3'
+Warning	1614	Converted to non-transactional lock on 't4'
 # Show that read locks on the base tables prohibit writing ...
 INSERT INTO t3 SELECT * FROM t4;
 ERROR HY000: Table 't3' was locked with a READ lock and can't be updated
@@ -196,7 +196,7 @@
 ## Report conversion on view due to existing non-transactional locks.
 LOCK TABLE v1 IN EXCLUSIVE MODE;
 Warnings:
-Warning	1613	Converted to non-transactional lock on 'v1'
+Warning	1614	Converted to non-transactional lock on 'v1'
 INSERT INTO t3 VALUES(333);
 INSERT INTO t4 VALUES(444);
 INSERT INTO t1 VALUES(111);
@@ -205,8 +205,8 @@
 ## Now report conversion on base table again.
 LOCK TABLE v1 IN EXCLUSIVE MODE;
 Warnings:
-Warning	1613	Converted to non-transactional lock on 't3'
-Warning	1613	Converted to non-transactional lock on 't4'
+Warning	1614	Converted to non-transactional lock on 't3'
+Warning	1614	Converted to non-transactional lock on 't4'
 INSERT INTO t3 VALUES(333);
 INSERT INTO t4 VALUES(444);
 INSERT INTO t1 VALUES(111);

mysqltest: Result content mismatch

Warnings from just before the error:
Note 1051 Unknown table 't1' 
Note 1051 Unknown table 't2' 
Note 1051 Unknown table 't3' 
Note 1051 Unknown table 't4' 
Note 1051 Unknown table 't5' 
Note 1051 Unknown table 't6' 
Note 1051 Unknown table 't7' 
Note 1051 Unknown table 't8' 

Stopping all servers...
Saving datadirs...
 - saving '/dev/shm/var-n_mix-110/mysqld.1'
 - saving '/dev/shm/var-n_mix-110/mysqld.2'
Resuming tests...

Retrying, attempt(1/3)...

Restarting all servers

How to repeat:
 WHERE: 6.0-rpl/sven Thu Jun 12 12:17:25 2008/all hosts and suites
 URL: https://intranet.mysql.com/secure/pushbuild/showpush.pl?dir=bzr_mysql-6.0-rpl&order=8
 --
 WHERE: 6.0-rpl/sven on Wed Jun 11 16:39:15 2008/'pb-valgrind-*' Valgrind/all suites
 URL: https://intranet.mysql.com/secure/pushbuild/showpush.pl?dir=bzr_mysql-6.0-rpl&order=5
 --
 Seen on many more locations too.
[17 Jul 2008 10:34] Alexander Nozdrin
A test case is disabled in 6.0 due to often failures.
[23 Sep 2008 13:37] Alexander Nozdrin
Patch: http://lists.mysql.com/commits/47401

Pushed into mysql-6.0-rpl.
[3 Oct 2008 7:38] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/55178

2698 Andrei Elkin	2008-10-03
      Bug #37712 rpl.rpl_locktrans_innodb fails sporadically on pushbuild
      
      The reason of the test failure was an inproper result file.
      
      That has been corrected with http://lists.mysql.com/commits/47401.
      The test is re-enabled.
[30 Jan 2009 13:29] Bugs System
Pushed into 6.0.10-alpha (revid:luis.soares@sun.com-20090129165607-wiskabxm948yx463) (version source revid:luis.soares@sun.com-20090129163120-e2ntks4wgpqde6zt) (merge vers: 6.0.10-alpha) (pib:6)
[30 Jan 2009 17:11] Paul Dubois
Test case changes. No changelog entry needed.