Details
-
Bug
-
Status: Open (View Workflow)
-
Critical
-
Resolution: Unresolved
-
11.4, 11.8
Description
Since MDEV-37152 the innodb.gap_locks test has been failing more.
At one point in 2023 this was occurring however it didn't occur for 2 years.
A failure example:
|
https://buildbot.mariadb.org/#/builders/840/builds/7182 |
|
|
|
|
CURRENT_TEST: innodb.gap_lock
|
--- /home/buildbot/amd64-sles-1506/build/mysql-test/suite/innodb/r/gap_locks.result 2025-09-30 06:33:16.000000000 +0000
|
+++ /home/buildbot/amd64-sles-1506/build/mysql-test/suite/innodb/r/gap_locks.reject 2025-09-30 08:13:36.796442832 +0000
|
@@ -8,28 +8,28 @@
|
DELETE FROM t1 WHERE b='2' AND c=2;
|
SHOW ENGINE INNODB STATUS;
|
Type Name Status
|
-InnoDB 2 lock struct(s), 1 row lock(s)
|
+InnoDB 0 lock struct(s), 0 row lock(s)
|
ROLLBACK;
|
SET TRANSACTION ISOLATION LEVEL REPEATABLE READ;
|
BEGIN;
|
DELETE FROM t1 WHERE b='2' AND c=2;
|
SHOW ENGINE INNODB STATUS;
|
Type Name Status
|
-InnoDB 2 lock struct(s), 1 row lock(s)
|
+InnoDB 0 lock struct(s), 0 row lock(s)
|
ROLLBACK;
|
SET TRANSACTION ISOLATION LEVEL READ COMMITTED;
|
BEGIN;
|
DELETE FROM t1 WHERE b='2' AND c=2;
|
SHOW ENGINE INNODB STATUS;
|
Type Name Status
|
-InnoDB 1 lock struct(s), 0 row lock(s)
|
+InnoDB 0 lock struct(s), 0 row lock(s)
|
ROLLBACK;
|
SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED;
|
This appeared after and during PR 4252 / MDEV-37152.
Attachments
Issue Links
- is caused by
-
-
- Closed
-
- is part of
-
MDEV-33073 always green buildbot
-
- Stalled
-