Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.1(EOL)
-
None
Description
|
Both InnoDB plugin and XtraDB |
storage_engine-innobase.foreign_keys [ fail ]
|
Test ended at 2015-08-24 15:27:02
|
|
|
CURRENT_TEST: storage_engine-innobase.foreign_keys
|
--- c:/buildbot/bbwin2/win-rqg-se/build-debug/mysql-test/suite/storage_engine/foreign_keys.result 2015-08-24 15:07:02.223385300 -0700
|
+++ c:\buildbot\bbwin2\win-rqg-se\build-debug\mysql-test\suite\storage_engine\foreign_keys.reject 2015-08-24 15:27:02.155382300 -0700
|
@@ -35,6 +35,14 @@
|
1 a
|
DROP TABLE t1;
|
ERROR 23000: Cannot delete or update a parent row: a foreign key constraint fails
|
+# ERROR: Statement ended with errno 1451, errname ER_ROW_IS_REFERENCED_2 (expected results: ER_ROW_IS_REFERENCED)
|
+# ------------ UNEXPECTED RESULT ------------
|
+# The statement|command finished with ER_ROW_IS_REFERENCED_2.
|
+# Foreign keys or the mix could be unsupported|malfunctioning, or the problem was caused by previous errors.
|
+# You can change the engine code, or create an rdiff, or disable the test by adding it to disabled.def.
|
+# Further in this test, the message might sometimes be suppressed; a part of the test might be skipped.
|
+# Also, this problem may cause a chain effect (more errors of different kinds in the test).
|
+# -------------------------------------------
|
DROP TABLE t2;
|
CREATE TABLE t2 (a <INT_COLUMN>,
|
b <CHAR_COLUMN>,
|
|
|
mysqltest: Result length mismatch
|
|
InnoDB, XtraDB, MyISAM |
storage_engine-innobase.type_spatial [ fail ]
|
Test ended at 2015-08-24 15:31:38
|
|
|
CURRENT_TEST: storage_engine-innobase.type_spatial
|
--- c:/buildbot/bbwin2/win-rqg-se/build-debug/mysql-test/suite/storage_engine/type_spatial.result 2015-08-24 15:07:03.299795400 -0700
|
+++ c:\buildbot\bbwin2\win-rqg-se\build-debug\mysql-test\suite\storage_engine\type_spatial.reject 2015-08-24 15:31:37.700754100 -0700
|
@@ -412,12 +412,12 @@
|
Intersects(g1.g, g2.g) as i, Crosses(g1.g, g2.g) as r
|
FROM gis_geometrycollection g1, gis_geometrycollection g2 ORDER BY first, second;
|
first second w c o e d t i r
|
-120 120 1 1 0 1 0 1 1 0
|
+120 120 1 1 0 1 0 0 1 0
|
120 121 0 0 1 0 0 0 1 0
|
120 122 NULL NULL NULL NULL NULL NULL NULL NULL
|
120 123 NULL NULL NULL NULL NULL NULL NULL NULL
|
121 120 0 0 1 0 0 0 1 0
|
-121 121 1 1 0 1 0 1 1 0
|
+121 121 1 1 0 1 0 0 1 0
|
121 122 NULL NULL NULL NULL NULL NULL NULL NULL
|
121 123 NULL NULL NULL NULL NULL NULL NULL NULL
|
122 120 NULL NULL NULL NULL NULL NULL NULL NULL
|
|
|
mysqltest: Result content mismatch
|
|
MyISAM |
storage_engine-myisam.type_spatial_indexes [ fail ]
|
Test ended at 2015-08-24 15:51:10
|
|
|
CURRENT_TEST: storage_engine-myisam.type_spatial_indexes
|
--- c:/buildbot/bbwin2/win-rqg-se/build-debug/mysql-test/suite/storage_engine/type_spatial_indexes.result 2015-08-24 15:07:03.299795400 -0700
|
+++ c:\buildbot\bbwin2\win-rqg-se\build-debug\mysql-test\suite\storage_engine\type_spatial_indexes.reject 2015-08-24 15:51:10.207694900 -0700
|
@@ -412,12 +412,12 @@
|
Intersects(g1.g, g2.g) as i, Crosses(g1.g, g2.g) as r
|
FROM gis_geometrycollection g1, gis_geometrycollection g2 ORDER BY first, second;
|
first second w c o e d t i r
|
-120 120 1 1 0 1 0 1 1 0
|
+120 120 1 1 0 1 0 0 1 0
|
120 121 0 0 1 0 0 0 1 0
|
120 122 NULL NULL NULL NULL NULL NULL NULL NULL
|
120 123 NULL NULL NULL NULL NULL NULL NULL NULL
|
121 120 0 0 1 0 0 0 1 0
|
-121 121 1 1 0 1 0 1 1 0
|
+121 121 1 1 0 1 0 0 1 0
|
121 122 NULL NULL NULL NULL NULL NULL NULL NULL
|
121 123 NULL NULL NULL NULL NULL NULL NULL NULL
|
122 120 NULL NULL NULL NULL NULL NULL NULL NULL
|
@@ -1112,22 +1112,22 @@
|
Intersects(g1.g, g2.g) as i, Crosses(g1.g, g2.g) as r
|
FROM gis_geometrycollection g1, gis_geometrycollection g2 ORDER BY first, second;
|
first second w c o e d t i r
|
-120 120 1 1 0 1 0 1 1 0
|
+120 120 1 1 0 1 0 0 1 0
|
120 121 0 0 1 0 0 0 1 0
|
-120 122 NULL NULL NULL NULL NULL NULL NULL NULL
|
-120 123 NULL NULL NULL NULL NULL NULL NULL NULL
|
+120 122 1 1 0 1 0 0 1 0
|
+120 123 1 1 0 1 0 0 1 0
|
121 120 0 0 1 0 0 0 1 0
|
-121 121 1 1 0 1 0 1 1 0
|
-121 122 NULL NULL NULL NULL NULL NULL NULL NULL
|
-121 123 NULL NULL NULL NULL NULL NULL NULL NULL
|
-122 120 NULL NULL NULL NULL NULL NULL NULL NULL
|
-122 121 NULL NULL NULL NULL NULL NULL NULL NULL
|
-122 122 NULL NULL NULL NULL NULL NULL NULL NULL
|
-122 123 NULL NULL NULL NULL NULL NULL NULL NULL
|
-123 120 NULL NULL NULL NULL NULL NULL NULL NULL
|
-123 121 NULL NULL NULL NULL NULL NULL NULL NULL
|
-123 122 NULL NULL NULL NULL NULL NULL NULL NULL
|
-123 123 NULL NULL NULL NULL NULL NULL NULL NULL
|
+121 121 1 1 0 1 0 0 1 0
|
+121 122 1 1 0 1 0 0 1 0
|
+121 123 1 1 0 1 0 0 1 0
|
+122 120 0 0 1 0 0 0 1 0
|
+122 121 1 1 0 1 0 0 1 0
|
+122 122 1 1 0 1 0 0 1 0
|
+122 123 1 1 0 1 0 0 1 0
|
+123 120 0 0 1 0 0 0 1 0
|
+123 121 1 1 0 1 0 0 1 0
|
+123 122 1 1 0 1 0 0 1 0
|
+123 123 1 1 0 1 0 0 1 0
|
DROP TABLE gis_point, gis_line, gis_polygon, gis_multi_point, gis_multi_line, gis_multi_polygon, gis_geometrycollection, gis_geometry;
|
USE gis_ogs;
|
# Lakes
|
|
|
mysqltest: Result length mismatch
|
Attachments
Issue Links
Activity
It was supposed to fail after fixing MDEV-8675. Earlier I had to disable the test for MyISAM, and since MyISAM was the only engine where the whole functionality of the test was applied, rdiffs for specific engines could not be used.
The test is re-enabled and fixed now. I'll keep Fix Version as 10.1.7 to avoid confusion.
https://github.com/MariaDB/server/commit/80089a60e5e38a3c38e23b8379ed1b5f592b0475
foreign_keys failure appeared since this commit:
commit 55b96d27089ee809dd0a4c9b3e0e3adb5a731bd4Author: Sergei Golubchik <serg@mariadb.org>Date: Sun Jun 28 08:51:53 2015 +0200bump the VERSION to 10.1.6 and related changesfix two #if MYSQL_VERSION_ID > 100105There were some changes to tests regarding FK errors, so apparentlythis one needs to be adjusted as well.
type_spatial appeared from this commit:
commit 37345bd9dde7fb948c439e73fbec5a88385162b2Author: Alexey Botchkov <holyfoot@askmonty.org>Date: Sun Mar 15 22:20:38 2015 +0400MDEV-7529 GIS: ST_Relate returns unexpected results for POINT relations.Problem was that we considered the point itself as the 'border' object. Insteadof that the 'border' of a POINT is an empty set, and the point is the 'interior'.Another error fixed by the way - not all operations of the resulting function were properlyallocated.The initial gis test was updated, this one should be too (it's partially based on gis.test).
type_spatial_indexes, in addition to the same problem as i type_spatial, also fails due to
MDEV-8675(only with MyISAM). The test should be disabled for MyISAM until the bug is fixed.