MySQL Bugs: #41498: concurrent_innodb_unsafelog fails sporadically: query should have had errno 1205

Bug #41498	concurrent_innodb_unsafelog fails sporadically: query should have had errno 1205
Submitted:	16 Dec 2008 12:36	Modified:	4 Aug 2009 23:28
Reporter:	Sven Sandberg	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Tests: Server	Severity:	S7 (Test Cases)
Version:		OS:	Any
Assigned to:	Horst Hunger	CPU Architecture:	Any
Tags:	concurrent_innodb_unsafelog, pushbuild, sporadic, test failure

Description:
sporadic pushbuild failure:

main.concurrent_innodb_unsafelog [ fail ]

mysqltest: In included file "./include/concurrent.inc": At line 543: query 'update t1 set tipo=1 where tipo=2' succeeded - should have failed with errno 1205...

The result from queries just before the failure was:
< snip >
** Set up table
SET SESSION STORAGE_ENGINE = InnoDB;
create table t1(eta int(11) not null, tipo int(11), c varchar(255));
insert into t1 values (7,7, "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa");
insert into t1 values (8,8, "bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb");
insert into t1 values (10,1,"ccccccccccccccccccccccccccccccccccccccccccc");
insert into t1 values (20,2,"ddddddddddddddddddddddddddddddddddddddddddd");
insert into t1 values (30,1,"eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee");
insert into t1 values (40,2,"fffffffffffffffffffffffffffffffffffffffffff");
insert into t1 values (50,1,"ggggggggggggggggggggggggggggggggggggggggggg");
insert into t1 values (60,2,"hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh");
insert into t1 values (70,1,"iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii");
insert into t1 values (80,22,"jjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjj");
insert into t1 values (90,11,"kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk");
** connection thread2
begin;
delete from t1 where tipo=2;
** connection thread1
begin;
update t1 set tipo=1 where tipo=2;

More results from queries before failure can be found in /dev/shm/var-embedded-112/log/concurrent_innodb_unsafelog.log

Stopping All Servers
Restoring snapshot of databases

How to repeat:
https://intranet.mysql.com/secure/pushbuild/showpush.pl?dir=bzr_mysql-5.1-telco-6.4&order=... debx86-b/embedded
xref: http://tinyurl.com/5pheke

BUG#40699 reports another problem with the same test.

and another tyupe of failure seen sporadically

--- /data0/pushbuild/pb/bzr_mysql-5.1-telco/11/mysql-5.1.32-ndb-6.3.23-pb11/mysql-test/r/concurrent_innodb_unsafelog.result	2009-02-17 14:01:02.000000000 +0300
+++ /data0/pushbuild/pb/bzr_mysql-5.1-telco/11/mysql-5.1.32-ndb-6.3.23-pb11/mysql-test/r/concurrent_innodb_unsafelog.reject	2009-02-17 15:32:58.000000000 +0300
@@ -71,7 +71,7 @@
 ** Release the lock and collect result from update on thread 2
 select release_lock("hello");
 release_lock("hello")
-1
+NULL
 ** Table should have eta updates where tipo=11 but updates made by
 ** thread 1 shouldn't be visible yet.
 select * from t1;

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/66658

2837 Tomas Ulin	2009-02-17
      Bug #41498 - disable test case
      modified:
        mysql-test/t/disabled.def

=== modified file 'mysql-test/t/disabled.def'
--- a/mysql-test/t/disabled.def	2009-02-02 11:17:23 +0000
+++ b/mysql-test/t/disabled.def	2009-02-17 13:42:16 +0000
@@ -13,3 +13,4 @@ kill                     : Bug#37780 200
 query_cache_28249        : Bug#41098 Query Cache returns wrong result with concurrent insert
 innodb_bug39438          : BUG#42383 2009-01-28 lsoares "This fails in embedded and on windows.  Note that this test is not run on windows and on embedded in PB for main trees currently"
 innodb			 : Bug #37995  	Error message truncation in test "innodb" in embedded mode
+concurrent_innodb_unsafelog: Bug #41498 concurrent_innodb_unsafelog fails sporadically

-- 
MySQL Code Commits Mailing List
For list archives: http://lists.mysql.com/commits
To unsubscribe:    http://lists.mysql.com/commits?unsub=commits@bugs.mysql.com

and another tyupe of failure seen sporadically

--- /data0/pushbuild/pb/bzr_mysql-5.1-telco/11/mysql-5.1.32-ndb-6.3.23-pb11/mysql-test/r/concurrent_innodb_unsafelog.result	2009-02-17 14:01:02.000000000 +0300
+++ /data0/pushbuild/pb/bzr_mysql-5.1-telco/11/mysql-5.1.32-ndb-6.3.23-pb11/mysql-test/r/concurrent_innodb_unsafelog.reject	2009-02-17 15:32:58.000000000 +0300
@@ -71,7 +71,7 @@
 ** Release the lock and collect result from update on thread 2
 select release_lock("hello");
 release_lock("hello")
-1
+NULL
 ** Table should have eta updates where tipo=11 but updates made by
 ** thread 1 shouldn't be visible yet.
 select * from t1;

Pushed into 5.1.32-ndb-6.4.3 (revid:tomas.ulin@sun.com-20090217134419-5ha6xg4dpedrbmau) (version source revid:tomas.ulin@sun.com-20090217134419-5ha6xg4dpedrbmau) (merge vers: 5.1.32-ndb-6.4.3) (pib:6)

Pushed into 5.1.32-ndb-6.2.17 (revid:tomas.ulin@sun.com-20090217134216-5699eq74ws4oxa0j) (version source revid:tomas.ulin@sun.com-20090217134216-5699eq74ws4oxa0j) (merge vers: 5.1.32-ndb-6.2.17) (pib:6)

Pushed into 5.1.32-ndb-6.3.23 (revid:tomas.ulin@sun.com-20090217134313-w3m03fjywc3pgzb6) (version source revid:tomas.ulin@sun.com-20090217134313-w3m03fjywc3pgzb6) (merge vers: 5.1.32-ndb-6.3.23) (pib:6)

Ok to push.  This test is fixed as part of BUG#39484: main.concurrent_innodb_safelog fails sporadically

Test case changes. No changelog entry needed.