Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Duplicate
-
10.6
-
None
Description
The failure can be reproduced with the following command:
./mtr --no-reorder gcol.gcol_purge innodb.gap_locks
|
The result is the following:
[Revision hash: b52b7b41296fa8857bcd2abc42f9ab6721b86f8b]
|
|
innodb.gap_locks 'innodb' w20 [ fail ]
|
Test ended at 2023-11-06 15:06:15
|
|
CURRENT_TEST: innodb.gap_locks
|
--- /home/buildbot/amd64-ubuntu-2004-debug/build/mysql-test/suite/innodb/r/gap_locks.result 2023-11-06 14:50:37.000000000 +0000
|
+++ /home/buildbot/amd64-ubuntu-2004-debug/build/mysql-test/suite/innodb/r/gap_locks.reject 2023-11-06 15:06:14.843197996 +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;
|
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 GLOBAL INNODB_STATUS_OUTPUT_LOCKS = @save_locks;
|
DROP TABLE t1;
|
|
mysqltest: Result content mismatch
|
|
Attachments
Issue Links
- duplicates
-
MDEV-28682 gcol.gcol_purge contaminates further execution of innodb.gap_locks
- Closed