Details
Description
See for example
http://buildbot.askmonty.org/buildbot/builders/kvm-bintar-centos5-amd64/builds/1272/steps/test/logs/stdio
CURRENT_TEST: main.innodb_mysql_lock mysqltest: At line 51: query 'INSERT INTO t1 VALUES (2)' succeeded - should have failed with errno 1213... The result from queries just before the failure was: # # 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);
Retry passed.
According to cross-reference, the failure has been happening since 2011, very rarely, several times a year at most, on different builders (deb, bintar, fulltest, windows), debug and release builds, ps-protocol and normal, always on the same statement.
Gliffy Diagrams
Attachments
Issue Links
- relates to
-
MDEV-7069 Fix buildbot failures in main server trees
-
- Stalled
-
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions