Regress failures against 9.4 development branch

[robe]

Debbie registered errors on last weekly regress against 9.4 I'll rerun these again later to verify they are still an issue: this was against r12337 Sunday postgresql 9.4 snapshot

Creating database 'postgis_reg' 
Loading PostGIS into 'postgis_reg' 
PostgreSQL 9.4devel on x86_64-unknown-linux-gnu, compiled by gcc (Debian 4.4.5-8) 4.4.5, 64-bit
  Postgis 2.2.0dev - r12337 - 2014-03-23 03:07:16
  scripts 2.2.0dev r12337
  GEOS: 3.4.3dev-CAPI-1.8.3 r3967
  PROJ: Rel. 4.7.1, 23 September 2009

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 
 loader/Latin1-implicit .... ok 
 dumper/literalsrid ....... ok 
 dumper/realtable ....... ok 
 binary .. ok 
 regress .. ok 
 regress_index .. failed (diff expected obtained: /var/lib/jenkins/workspace/postgis/regress_pgdev/tmp/2_2_pg9.4w64/test_28_diff)
 regress_index_nulls .. ok 
 regress_selectivity .. ok 
 lwgeom_regress .. ok 
 regress_lrs .. ok 
 removepoint .. ok 
 setpoint .. ok 
 simplify .. ok 
 snaptogrid .. ok 
 summary .. ok 
 affine .. ok 
 empty .. ok 
 forcecurve .. 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: /var/lib/jenkins/workspace/postgis/regress_pgdev/tmp/2_2_pg9.4w64/test_74_diff)
 typmod .. ok 
 remove_repeated_points .. ok 
 split .. ok 
 relate .. ok 
 bestsrid .. ok 
 concave_hull .. ok 
 twkb .. ok 
 hausdorff .. ok 
 regress_buffer_params .. ok 
 offsetcurve .. ok 
 relatematch .. ok 
 isvaliddetail .. ok 
 sharedpaths .. ok 
 snap .. ok 
 node .. ok 
 unaryunion .. ok 
 clean .. failed (diff expected obtained: /var/lib/jenkins/workspace/postgis/regress_pgdev/tmp/2_2_pg9.4w64/test_91_diff)
 relate_bnr .. ok 
 delaunaytriangles .. ok 
 in_geojson .. ok 
 uninstall .. ok (4226)

regress failure outputs below:

--- regress_index_expected	2014-01-15 22:24:34.000000000 -0800
+++ /var/lib/jenkins/workspace/postgis/regress_pgdev/tmp/2_2_pg9.4w64/test_28_out	2014-03-22 20:08:45.000000000 -0700
@@ -1,3 +1,4 @@
+COPY 50000
 2594|POINT(130.504303 126.53112)
 3618|POINT(130.447205 131.655289)
 7245|POINT(128.10466 130.94133)

--- tickets_expected	2014-02-08 20:06:27.000000000 -0800
+++ /var/lib/jenkins/workspace/postgis/regress_pgdev/tmp/2_2_pg9.4w64/test_74_out	2014-03-22 20:08:53.000000000 -0700
@@ -188,6 +188,7 @@
 #745|GEOMETRYCOLLECTION(POLYGON((-72 42 1,-70 43 1,-71 41 1,-72 42 1)))
 #1450|POINT|POLYGON
 #1482|4326
+COPY 2
 #852.1|1|f|f
 #852.1|2|f|f
 #852.2|1|t|t

--- clean_expected	2014-01-15 22:24:34.000000000 -0800
+++ /var/lib/jenkins/workspace/postgis/regress_pgdev/tmp/2_2_pg9.4w64/test_91_out	2014-03-22 20:09:02.000000000 -0700
@@ -1,3 +1,4 @@
+COPY 28
 RT|1|t|t|f
 RT|2|t|t|f
 RT|3|t|t|f

looks like some new output from new psql — COPY

[robe]

I'm switching this to a blocker. though seems like a trivial issue, we can't very well release a 2.2 that doesn't even pass make check on 9.4. 9.4 is planned to be released in 3rd quarter 2014. If we can't make a release for 2.2 by then, we are going to have do another 2.1 release and backport whatever fix we have here.

[robe]

I think I have made 9.4 happy again.

changed in r12482 and r12843 . Someone should probably check I did the right thing since I had to remove one set of copies from regress. I feel so dirty touching perl code

[robe]

oops second change was r12483 (dyslexic typo)

[robe]

I'm reopening this since we need to backport the fix to 2.1 since we won't have 2.2 ready in time for 9.4.

[robe]

Hmm they might have changed things in 9.4beta2 because just added 9.4beta2 to 2.1.4 regress test chain and debbie and it seemed to regress fine without any change.