Details
Description
Test failure:
main.mdl_sync w3 [ fail ]
|
Test ended at 2025-04-19 06:40:48
|
CURRENT_TEST: main.mdl_sync
|
Warning: /home/buildbot/amd64-debian-12-debug-embedded/build/libmysqld/examples/mariadb-test-embedded: unknown option '--loose-disable-ssl-verify-server-cert'
|
Warning: /home/buildbot/amd64-debian-12-debug-embedded/build/libmysqld/examples/mariadb-test-embedded: unknown variable 'loose-ssl-ca=/home/buildbot/amd64-debian-12-debug-embedded/build/mysql-test/std_data/cacert.pem'
|
Warning: /home/buildbot/amd64-debian-12-debug-embedded/build/libmysqld/examples/mariadb-test-embedded: unknown variable 'loose-ssl-cert=/home/buildbot/amd64-debian-12-debug-embedded/build/mysql-test/std_data/client-cert.pem'
|
Warning: /home/buildbot/amd64-debian-12-debug-embedded/build/libmysqld/examples/mariadb-test-embedded: unknown variable 'loose-ssl-key=/home/buildbot/amd64-debian-12-debug-embedded/build/mysql-test/std_data/client-key.pem'
|
Warning: /home/buildbot/amd64-debian-12-debug-embedded/build/libmysqld/examples/mariadb-test-embedded: unknown option '--loose-skip-ssl'
|
Got ERROR: "Failed to write to mysql.general_log: Wait on a lock was aborted due to a pending exclusive lock" errno: 2000
|
--- /home/buildbot/amd64-debian-12-debug-embedded/build/mysql-test/main/mdl_sync.result 2025-04-19 06:35:23.000000000 +0000
|
+++ /home/buildbot/amd64-debian-12-debug-embedded/build/mysql-test/main/mdl_sync.reject 2025-04-19 06:40:47.527987500 +0000
|
@@ -2459,6 +2459,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 t2
|
unlock tables;
|
connection default;
|
# Reaping UPDATE
|
Another variant of this failure (--ps-protocol):
mysqltest: At line 3161: The result of the 1st execution does not match with
|
the result of the 2nd execution of ps-protocol:
|
1st:
|
LOCK_MODE LOCK_TYPE TABLE_SCHEMA TABLE_NAME
|
MDL_BACKUP_FTWRL2 Backup lock
|
MDL_SHARED Table metadata lock test t2
|
|
2nd:
|
LOCK_MODE LOCK_TYPE TABLE_SCHEMA TABLE_NAME
|
MDL_BACKUP_FTWRL2 Backup lock
|
Reported basing on this build.
Cross reference shows more failures.
Attachments
Issue Links
- is part of
-
MDEV-33073 always green buildbot
-
- Stalled
-
-
MDEV-36647 No red leaves in the forest
-
- Open
-
Some unsuccessful attempts to get it fixed:
commit e996f77cd8716320dc132bd63a252a4b5bb1366e
Author: Thirunarayanan Balathandayuthapani <thiru@mariadb.com>
Date: Wed Nov 29 17:43:40 2023 +0530
MDEV-32897 main suite test case prints extra row for metadata_lock_info query
- Added the parameter stats_persistent=0 for InnoDB engine.
- Before printing metadata_lock_info query, make sure that
InnoDB does complete purging.
Reviewed by: Marko Mäkelä
commit a7bf0a42d0c1a5540c0b32a8284c1462d7c8c9a8
Author: Sergei Golubchik <serg@mariadb.org>
Date: Sat Apr 6 23:05:57 2024 +0200
sporadic failures of main.mdl_sync
main.mdl_sync 'innodb' w32 [ fail ]
Test ended at 2024-04-06 14:11:15
CURRENT_TEST: main.mdl_sync
--- main/mdl_sync.result
+++ main/mdl_sync.reject
@@ -2458,6 +2458,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 t2
unlock tables;
connection default;
# Reaping UPDATE