[MDEV-22947] main.innodb_mysql_lock fails sporadically in buildbot (backport MDEV-7861) Created: 2020-06-19  Updated: 2023-11-29  Resolved: 2023-11-29

Status: Closed
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 10.1, 10.2
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-7861 main.innodb_mysql_lock fails sporadic... Closed

 Description   

MDEV-7861 says it was pushed to 10.2, but according to git history, it only made it to 10.3. So, the test still fails the same way in 10.1-10.2. The fix should be backported at least to 10.2, and maybe in 10.1 if it's still alive by then.

http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest/builds/23928

main.innodb_mysql_lock 'xtradb'          w2 [ fail ]
        Test ended at 2020-06-07 08:43:06
 
CURRENT_TEST: main.innodb_mysql_lock
mysqltest: At line 55: query 'INSERT INTO t1 VALUES (2)' succeeded - should have failed with errno 1213...
 
The result from queries just before the failure was:
< snip >
#
# Bug #22876 Four-way deadlock
#
DROP TABLE IF EXISTS t1;
# Connection 1
set @@autocommit=0;
CREATE TABLE t1(s1 INT UNIQUE) ENGINE=innodb;
INSERT INTO t1 VALUES (1);
# Connection 2
set @@autocommit=0;
INSERT INTO t1 VALUES (2);
INSERT INTO t1 VALUES (1);
# Connection 3
set @@autocommit=0;
DROP TABLE t1;
# Connection 1
# Connection 1 is now holding the lock.
# Issuing insert from connection 1 while connection 2&3 
# is waiting for the lock should give a deadlock error.
INSERT INTO t1 VALUES (2);


Generated at Thu Feb 08 09:18:41 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.