Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
5.5(EOL), 10.0(EOL), 10.1(EOL), 10.2(EOL), 10.3(EOL)
Description
innodb.dml_purge '64k,innodb' w3 [ fail ]
|
Test ended at 2017-08-20 16:06:45
|
|
CURRENT_TEST: innodb.dml_purge
|
--- /usr/share/mysql/mysql-test/suite/innodb/r/dml_purge.result 2017-08-20 14:24:53.000000000 -0400
|
+++ /dev/shm/var/3/log/dml_purge.reject 2017-08-20 16:06:45.122366993 -0400
|
@@ -15,8 +15,8 @@
|
DB_ROLL_PTR=0x80000000000000,
|
b=0x80000002)
|
header=0x000018090074 (a=0x80000003,
|
- DB_TRX_ID=0x000000000000,
|
- DB_ROLL_PTR=0x80000000000000,
|
+ DB_TRX_ID=0x000000000506,
|
+ DB_ROLL_PTR=0x04000001370317,
|
b=0x7ffffffd)
|
header=0x030008030000 (a=0x73757072656d756d00)
|
SELECT * FROM t1;
|
|
mysqltest: Result content mismatch
|
Attachments
Issue Links
- is caused by
-
MDEV-11802 innodb.innodb_bug14676111 fails in buildbot due to InnoDB purge failing to start when there is work to do
- Closed
- is duplicated by
-
MDEV-14445 innodb.table_flags failed in buildbot with wrong result
- Closed
- relates to
-
MDEV-11802 innodb.innodb_bug14676111 fails in buildbot due to InnoDB purge failing to start when there is work to do
- Closed
-
MDEV-13039 innodb_fast_shutdown=0 may fail to purge all undo logs
- Closed
-
MDEV-17049 Enable --suite=innodb_undo on buildbot
- Closed
-
MDEV-11802 innodb.innodb_bug14676111 fails in buildbot due to InnoDB purge failing to start when there is work to do
- Closed
-
MDEV-13697 DB_TRX_ID is not always reset when the history is removed
- Closed
-
MDEV-14080 InnoDB shutdown sometimes hangs
- Closed
- mentioned in
-
Page Loading...