Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Cannot Reproduce
-
10.1(EOL)
-
None
Description
http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest2/builds/11476/steps/mtr_nm/logs/stdio
innodb.innodb_max_recordsize_64k 'xtradb' w3 [ fail ]
|
Test ended at 2018-02-03 14:09:55
|
|
CURRENT_TEST: innodb.innodb_max_recordsize_64k
|
--- /mnt/buildbot/build/mariadb-10.1.31/mysql-test/suite/innodb/r/innodb_max_recordsize_64k.result 2018-02-03 11:41:55.000000000 +0200
|
+++ /mnt/buildbot/build/mariadb-10.1.31/mysql-test/suite/innodb/r/innodb_max_recordsize_64k.reject 2018-02-03 14:09:55.000000000 +0200
|
@@ -539,10 +539,10 @@
|
test.t analyze status OK
|
SELECT stat_value FROM mysql.innodb_index_stats where database_name = 'test' and table_name= 't' and stat_name='n_leaf_pages';
|
stat_value
|
-4
|
+2
|
SELECT clustered_index_size from mysql.innodb_table_stats where database_name = 'test' and table_name= 't';
|
clustered_index_size
|
-5
|
+3
|
DROP TABLE t;
|
CREATE TABLE t(col BLOB) ENGINE=InnoDB ROW_FORMAT=REDUNDANT;
|
SHOW WARNINGS;
|
|
mysqltest: Result content mismatch
|
Attachments
Issue Links
- relates to
-
MDEV-7142 main.index_merge_innodb fails sporadically in buildbot with wrong result or timeout
- Closed
-
MDEV-10682 Race condition between ANALYZE TABLE and STATS_AUTO_RECALC
- Closed