Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.5
-
None
Description
http://buildbot.askmonty.org/buildbot/builders/winx64-debug/builds/21598/steps/test/logs/stdio
innodb.ibuf_not_empty 'innodb,strict_crc32' w4 [ fail ]
|
Test ended at 2020-10-24 09:56:28
|
|
CURRENT_TEST: innodb.ibuf_not_empty
|
--- D:/winx64-debug/build/src/mysql-test/suite/innodb/r/ibuf_not_empty.result 2020-10-24 09:40:27.610487900 +0000
|
+++ D:\winx64-debug\build\src\mysql-test\suite\innodb\r\ibuf_not_empty.reject 2020-10-24 09:56:28.715051700 +0000
|
@@ -9,7 +9,7 @@
|
# restart: --innodb-force-recovery=6 --innodb-change-buffer-dump
|
check table t1;
|
Table Op Msg_type Msg_text
|
-test.t1 check Warning InnoDB: Index 'b' contains 990 entries, should be 1024.
|
+test.t1 check Warning InnoDB: Index 'b' contains 991 entries, should be 1024.
|
test.t1 check error Corrupt
|
# restart
|
SET GLOBAL innodb_fast_shutdown=0;
|
|
mysqltest: Result content mismatch
|
Attachments
Issue Links
- relates to
-
MDEV-19021 innodb.ibuf_not_empty failed in buildbot with wrong result
- Closed
-
MDEV-23399 10.5 performance regression with IO-bound tpcc
- Closed