Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.5, 10.2(EOL), 10.3(EOL), 10.4(EOL)
-
None
Description
http://buildbot.askmonty.org/buildbot/builders/kvm-rpm-centos74-amd64-debug/builds/755
gcol.innodb_virtual_debug_purge 'innodb' w3 [ fail ]
|
Test ended at 2018-08-10 21:48:13
|
|
CURRENT_TEST: gcol.innodb_virtual_debug_purge
|
--- /usr/share/mysql-test/suite/gcol/r/innodb_virtual_debug_purge.result 2018-08-10 19:08:32.000000000 +0000
|
+++ /dev/shm/var/3/log/innodb_virtual_debug_purge.reject 2018-08-10 21:48:13.389484458 +0000
|
@@ -200,7 +200,7 @@
|
disconnect prevent_purge;
|
connection default;
|
SET DEBUG_SYNC='now WAIT_FOR purge_start';
|
-InnoDB 1 transactions not purged
|
+InnoDB 2 transactions not purged
|
SET DEBUG_SYNC='now SIGNAL release';
|
SET GLOBAL debug_dbug=@old_dbug;
|
connection truncate;
|
|
mysqltest: Result content mismatch
|
|
- skipping '/dev/shm/var/3/log/gcol.innodb_virtual_debug_purge-innodb/'
|
|
Retrying test gcol.innodb_virtual_debug_purge, attempt(2/3)...
|
Attachments
Issue Links
- causes
-
MDEV-31813 SET GLOBAL innodb_max_purge_lag_wait=… hangs if innodb_read_only=ON
- Closed
- relates to
-
MDEV-15912 InnoDB: Failing assertion: purge_sys.tail.commit <= purge_sys.rseg->last_commit upon upgrade from 10.0 or 10.1 to 10.3
- Closed
-
MDEV-17745 innodb.innodb_stats_persistent failed in buildbot with wrong result
- Closed
-
MDEV-22958 innodb.instant_alter_debug fails in buildbot with wrong result
- Closed