[MDEV-25473] main.deadlock_innodb Created: 2021-04-21  Updated: 2021-04-21

Status: Open
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 10.2.37
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Andrei Elkin Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Environment:

intel-bbw1-docker-fedora-33 https://buildbot.mariadb.org/#/workers/155

git commit id: ef2749c90d7



 Description   

The test failed on new BB with the following trace:

main.deadlock_innodb 'innodb'            w32 [ fail ]
        Test ended at 2021-04-21 10:51:03
 
CURRENT_TEST: main.deadlock_innodb
mysqltest: In included file "/buildbot/amd64-fedora-33/build/mysql-test/include/deadlock.inc": 
included from /buildbot/amd64-fedora-33/build/mysql-test/t/deadlock_innodb.test at line 17:
At line 82: query 'reap' failed: 1205: Lock wait timeout exceeded; try restarting transaction
 
The result from queries just before the failure was:
< snip >
select * from t2;
b	a
0	100
1	20
2	30
select * from t1;
id	x
0	0
300	300
connection con2;
set autocommit=0;
update t1 set x=2 where id = 0;
connection con1;
update t1 set x=1 where id = 0;
select * from t1;
id	x
0	1
300	300
commit;
connection con2;
 
More results from queries before failure can be found in /buildbot/amd64-fedora-33/build/mysql-test/var/32/log/deadlock_innodb.log

to succeed at retrying

main.deadlock_innodb 'innodb'            w32 [ retry-pass ] 

More details are available at https://buildbot.mariadb.org/#/builders/196/builds/2090.


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