[MDEV-22954] main.mdl fails in buildbot with wrong result Created: 2020-06-19  Updated: 2022-07-08  Resolved: 2022-07-08

Status: Closed
Project: MariaDB Server
Component/s: Locking, Tests
Affects Version/s: 10.5
Fix Version/s: 10.5.17

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Vladislav Vaintroub
Resolution: Fixed Votes: 0
Labels: None


 Description   

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

10.5 fd1755e49de98148d261d4fdfebe09fa

main.mdl 'innodb'                        w2 [ fail ]
        Test ended at 2020-06-12 21:05:42
 
CURRENT_TEST: main.mdl
--- /usr/share/mysql-test/main/mdl.result	2020-06-12 18:18:50.000000000 +0000
+++ /dev/shm/var/2/log/mdl.reject	2020-06-12 21:05:41.868178883 +0000
@@ -81,6 +81,7 @@
 SELECT LOCK_MODE, LOCK_TYPE, TABLE_SCHEMA, TABLE_NAME FROM information_schema.metadata_lock_info;
 LOCK_MODE	LOCK_TYPE	TABLE_SCHEMA	TABLE_NAME
 MDL_BACKUP_FTWRL2	Backup lock		
+MDL_SHARED	Table metadata lock	test	t1
 MDL_SHARED_WRITE	Table metadata lock	test	t3
 unlock tables;
 connection locker;
 
mysqltest: Result length mismatch



 Comments   
Comment by Elena Stepanova [ 2020-06-19 ]

http://buildbot.askmonty.org/buildbot/builders/kvm-bintar-centos6-x86/builds/1230

main.create_or_replace 'innodb'          w3 [ fail ]
        Test ended at 2020-06-17 19:53:04
 
CURRENT_TEST: main.create_or_replace
--- /usr/local/mariadb-10.5.4-linux-i686/mysql-test/main/create_or_replace.result	2020-06-17 18:39:58.000000000 +0300
+++ /usr/local/mariadb-10.5.4-linux-i686/mysql-test/main/create_or_replace.reject	2020-06-17 19:53:04.309107241 +0300
@@ -265,6 +265,7 @@
 #	MDL_BACKUP_DML	NULL	Backup lock		
 #	MDL_INTENTION_EXCLUSIVE	NULL	Schema metadata lock	mysqltest2	
 #	MDL_INTENTION_EXCLUSIVE	NULL	Schema metadata lock	test	
+#	MDL_SHARED	NULL	Table metadata lock	test	t4
 #	MDL_SHARED_NO_READ_WRITE	NULL	Table metadata lock	mysqltest2	t2
 #	MDL_SHARED_NO_READ_WRITE	NULL	Table metadata lock	test	t1
 create or replace table test.t1;
 
mysqltest: Result length mismatch

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