[MDEV-22511] innodb.truncate_foreign failed in buildbot with wrong error code Created: 2020-05-09  Updated: 2020-07-31  Resolved: 2020-07-31

Status: Closed
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 10.2
Fix Version/s: 10.2.33, 10.3.24, 10.4.14, 10.5.5

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Thirunarayanan Balathandayuthapani
Resolution: Fixed Votes: 0
Labels: None


 Description   

Note: Possibly it has already been fixed, but I don't see a clear indication of it.

http://buildbot.askmonty.org/buildbot/builders/kvm-rpm-centos74-amd64-debug/builds/3972

bb-10.2-release f509169d342e1395ae80581ca1056515 2020-05-06 21:09:56

innodb.truncate_foreign 'innodb'         w2 [ fail ]
        Test ended at 2020-05-06 18:44:48
 
CURRENT_TEST: innodb.truncate_foreign
mysqltest: At line 41: query 'TRUNCATE TABLE child' succeeded - should have failed with errno 1205...
 
The result from queries just before the failure was:
< snip >
a
2
connect  dml,localhost,root;
SET DEBUG_SYNC='foreign_constraint_update_cascade SIGNAL fk WAIT_FOR go';
UPDATE parent SET a=3;
connection default;
SET DEBUG_SYNC='now WAIT_FOR fk';
SET lock_wait_timeout=1;
TRUNCATE TABLE child;
ERROR HY000: Lock wait timeout exceeded; try restarting transaction
SET DEBUG_SYNC='now SIGNAL go';
connection dml;
SELECT * FROM child;
a
3
SET DEBUG_SYNC='foreign_constraint_check_for_update SIGNAL fk WAIT_FOR go';
DELETE FROM parent;
connection default;
SET DEBUG_SYNC='now WAIT_FOR fk';
TRUNCATE TABLE child;


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