Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Won't Fix
-
10.2(EOL), 10.3(EOL), 10.4(EOL), 10.5
-
None
Description
http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest2/builds/11336/steps/mtr_nm/logs/stdio
innodb_gis.rtree_recovery 'innodb' w1 [ fail ]
|
Test ended at 2018-01-25 15:21:01
|
|
CURRENT_TEST: innodb_gis.rtree_recovery
|
--- /mnt/buildbot/build/mariadb-10.2.13/mysql-test/suite/innodb_gis/r/rtree_recovery.result 2018-01-25 11:38:02.000000000 +0200
|
+++ /mnt/buildbot/build/mariadb-10.2.13/mysql-test/suite/innodb_gis/r/rtree_recovery.reject 2018-01-25 15:21:00.000000000 +0200
|
@@ -19,7 +19,8 @@
|
COMMIT;
|
check table t1;
|
Table Op Msg_type Msg_text
|
-test.t1 check status OK
|
+test.t1 check Warning InnoDB: Index 'c2' contains 551 entries, should be 367.
|
+test.t1 check error Corrupt
|
drop table t1;
|
create table t1 (c1 int, c2 point not null, spatial index (c2))engine=innodb;
|
CALL insert_t1(367);
|
|
mysqltest: Result length mismatch
|
Attachments
Issue Links
- relates to
-
MDEV-12353 Efficient InnoDB redo log record format
- Closed