regress failure on windows 7 32-bit 9.3 beta 1 EDB

[robe]

Related to this ticket, I too am getting failures on my windows 7 32-bit 9.3 setup:

PostgreSQL 9.3beta1, compiled by Visual C++ build 1600, 32-bit
 - 2013-08-06 15:25:47
  GEOS: 3.4.0dev-CAPI-1.8.0 r3829
  PROJ: Rel. 4.8.0, 6 March 2012

Running tests

 loader/Point .............. ok
 loader/PointM .............. ok
 loader/PointZ .............. ok
 loader/MultiPoint .............. ok
 loader/MultiPointM .............. ok
 loader/MultiPointZ .............. ok
 loader/Arc .............. ok
 loader/ArcM .............. ok
 loader/ArcZ .............. ok
 loader/Polygon .............. ok
 loader/PolygonM .............. ok
 loader/PolygonZ .............. ok
 loader/TSTPolygon ......... ok
 loader/TSIPolygon ......... ok
 loader/TSTIPolygon ......... ok
 loader/PointWithSchema ..... ok
 loader/NoTransPoint ......... ok
 loader/NotReallyMultiPoint ......... ok
 loader/MultiToSinglePoint ......... ok
 loader/ReprojectPts ........ ok
 loader/ReprojectPtsGeog ........ ok
 loader/Latin1 .... ok
 binary .. ok
 regress .. ok
 regress_index .. ok
 regress_index_nulls .. failed (diff expected obtained: /projects/postgis/tmp/2.
1.0_pg9.3w32/test_26_diff)
 regress_selectivity .. ok
 lwgeom_regress .. ok
 regress_lrs .. ok
 removepoint .. ok
 setpoint .. ok
 simplify .. ok
 snaptogrid .. ok
 summary .. ok
 affine .. ok
 empty .. ok
 measures .. ok
 legacy .. ok
 long_xact .. ok
 ctors .. ok
 sql-mm-serialize .. ok
 sql-mm-circularstring .. ok
 sql-mm-compoundcurve .. ok
 sql-mm-curvepoly .. ok
 sql-mm-general .. ok
 sql-mm-multicurve .. ok
 sql-mm-multisurface .. ok
 polyhedralsurface .. ok
 polygonize .. ok
 postgis_type_name .. ok
 geography .. ok
 out_geometry .. ok
 out_geography .. ok
 in_geohash .. ok
 in_gml .. ok
 in_kml .. ok
 iscollection .. ok
 regress_ogc .. ok
 regress_ogc_cover .. ok
 regress_ogc_prep .. ok
 regress_bdpoly .. ok
 regress_proj .. ok
 regress_management .. ok
 dump .. ok
 dumppoints .. ok
 boundary .. ok
 wmsservers .. ok
 wkt .. ok
 wkb .. ok
 tickets .. failed (diff expected obtained: /projects/postgis/tmp/2.1.0_pg9.3w32
/test_70_diff)
 typmod .. ok
 remove_repeated_points .. ok
 split .. ok
 relate .. ok
 bestsrid .. ok
 concave_hull .. ok
 hausdorff .. ok
 regress_buffer_params .. ok
 offsetcurve .. ok
 relatematch .. ok
 isvaliddetail .. ok
 sharedpaths .. ok
 snap .. ok
 node .. ok
 unaryunion .. ok
 clean .. ok
 relate_bnr .. ok
 delaunaytriangles .. ok
 in_geojson .. ok
)uninstall .. ok (4112

Run tests: 90
Failed: 2
Makefile:203: recipe for target `check' failed
make[1]: *** [check] Error 2
make[1]: Leaving directory `/projects/postgis/branches/2.1/regress'
GNUmakefile:14: recipe for target `check' failed
make: *** [check] Error 1

--- regress_index_nulls_expected	2013-07-09 12:31:43 -0400
+++ /projects/postgis/tmp/2.1.0_pg9.3w32/test_26_out	2013-08-06 11:30:43 -0400
@@ -1,4 +1,6 @@
 NOTICE:  table "indexnulls" does not exist, skipping
+ERROR:  parse error - invalid geometry at character 88
 NOTICE:  table "indexnulls" does not exist, skipping
+ERROR:  parse error - invalid geometry at character 87
 NOTICE:  table "indexempty" does not exist, skipping
 NOTICE:  table "indexempty" does not exist, skipping

--- tickets_expected	2013-07-09 12:31:30 -0400
+++ /projects/postgis/tmp/2.1.0_pg9.3w32/test_70_out	2013-08-06 11:30:57 -0400
@@ -121,7 +121,7 @@
 ERROR:  Shell is not a line
 #695
 ERROR:  First argument must be a LINESTRING
-#696|010F000080060000000103000080010000000500000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000F03F0000000000000000000000000000F03F000000000000F03F0000000000000000000000000000F03F0000000000000000000000000000000000000000000000000000000000000000010300008001000000050000000000000000000000000000000000000000000000000000000000000000000000000000000000F03F0000000000000000000000000000F03F000000000000F03F0000000000000000000000000000F03F0000000000000000000000000000000000000000000000000000000000000000000000000000000001030000800100000005000000000000000000000000000000000000000000000000000000000000000000F03F00000000000000000000000000000000000000000000F03F0000000000000000000000000000F03F00000000000000000000000000000000000000000000F03F00000000000000000000000000000000000000000000000001030000800100000005000000000000000000F03F000000000000F03F0000000000000000000000000000F03F000000000000F03F000000000000F03F000000000000F03F0000000000000000000000000000F03F000000000000F03F00000000000000000000000000000000000000000000F03F000000000000F03F0000000000000000010300008001000000050000000000000000000000000000000000F03F00000000000000000000000000000000000000000000F03F000000000000F03F000000000000F03F000000000000F03F000000000000F03F000000000000F03F000000000000F03F00000000000000000000000000000000000000000000F03F00000000000000000103000080010000000500000000000000000000000000000000000000000000000000F03F000000000000F03F0000000000000000000000000000F03F000000000000F03F000000000000F03F000000000000F03F0000000000000000000000000000F03F000000000000F03F00000000000000000000000000000000000000000000F03F
+ERROR:  parse error - invalid geometry
 #720|MULTIPOINT(-1113194.91 4838471.4,-1113194.91 7326837.72,-1113194.91 11028513.63,556597.45 4838471.4,556597.45 7326837.72,556597.45 11028513.63,2226389.82 4838471.4,2226389.82 7326837.72,2226389.82 11028513.63,3896182.18 4838471.4,3896182.18 7326837.72,3896182.18 11028513.63,5565974.54 4838471.4,5565974.54 7326837.72,5565974.54 11028513.63)
 #723|0101000020E61000006284F068E33826C00000000000004440
 #723|0107000020E610000000000000
@@ -219,7 +219,7 @@
 #1697.2|0
 #1697.3|1024
 #1734.1|1026
-#1755|01010000A0E6100000000000000040554000000000008041400000000000000000
+ERROR:  parse error - invalid geometry
 #1776|POLYGON((0 0,10 0,10 10,0 0))|POLYGON((0 0,10 0,10 10,0 0))
 #1780|t
 #1791|4.7

test 26 seems like harmless character position difference but the tickets (test 70) has me a bit concerned.

I'm going to retest with beta2 to see if the error goes away

[robe]

actually test_26 I misread on closer inspection is not a mere difference in character position.

[robe]

this only happens on my 32-bit windows 7 OS. Might be something else since that one is a mess. Pushing for now.

[robe]

I actually don't get this error anymore on the windows 7 32-bit I was testing. So not sure what caused it.