Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.2(EOL)
Description
vcol.vcol_keys_myisam w3 [ fail ]
|
Test ended at 2017-01-18 15:36:04
|
|
CURRENT_TEST: vcol.vcol_keys_myisam
|
myisamchk: error: 138 when opening MyISAM-table '/usr/local/mariadb-10.2.4-linux-x86_64/mysql-test/var/3/mysqld.1/data//test/t1'
|
myisamchk: error: 138 when opening MyISAM-table '/usr/local/mariadb-10.2.4-linux-x86_64/mysql-test/var/3/mysqld.1/data//test/t1'
|
--- /usr/local/mariadb-10.2.4-linux-x86_64/mysql-test/suite/vcol/r/vcol_keys_myisam.result 2017-01-18 14:36:57.000000000 +0100
|
+++ /usr/local/mariadb-10.2.4-linux-x86_64/mysql-test/suite/vcol/r/vcol_keys_myisam.reject 2017-01-18 15:36:04.000000000 +0100
|
@@ -178,11 +178,13 @@
|
DELETE FROM t1 WHERE f5 = 1 OR v4 = 4 ORDER BY f5,v4 LIMIT 9;
|
SELECT * from t1;
|
f2 f3 f4 f5 v4
|
+5 4 1 0 4
|
5 7 NULL 0 5
|
5 4 0 4 5
|
5 7 0 7 5
|
5 0 0 4 5
|
5 0 0 7 5
|
+5 4 4 4 4
|
5 7 7 7 7
|
5 1 1 0 1
|
DROP TABLE t1;
|
|
mysqltest: Result length mismatch
|
Reproducible locally on my machine, but only on a release build.