[MDEV-22958] innodb.instant_alter_debug fails in buildbot with wrong result - Jira

XML

Word

Printable

10.5 359d5f56c315cbc428e96d5d2d83d5a7
innodb.instant_alter_debug 'innodb' w4 [ fail ]
Test ended at 2020-06-15 16:15:58

CURRENT_TEST: innodb.instant_alter_debug
--- D:/winx64-debug/build/src/mysql-test/suite/innodb/r/instant_alter_debug.result 2020-06-15 15:19:41.830087100 +0000
+++ D:\winx64-debug\build\src\mysql-test\suite\innodb\r\instant_alter_debug.reject 2020-06-15 16:15:57.896423800 +0000
@@ -204,7 +204,7 @@
COMMIT;
connection default;
SET DEBUG_SYNC = 'now WAIT_FOR copied';
-InnoDB 1 transactions not purged
+InnoDB 2 transactions not purged
INSERT INTO t1 SET a=1;
INSERT INTO t1 SET a=2,b=3,c=4;
SET DEBUG_SYNC = 'now SIGNAL logged';

mysqltest: Result content mismatch

relates to

MDEV-16678 Use MDL for innodb background threads instead of dict_operation_lock

MDEV-16952 Introduce SET GLOBAL innodb_max_purge_lag_wait

MDEV-17745 innodb.innodb_stats_persistent failed in buildbot with wrong result