Opened 6 years ago

Closed 5 years ago

#4376 closed defect (fixed)

regress tickets failure nan nan

Reported by: robe Owned by: pramsey
Priority: blocker Milestone: PostGIS 3.0.0
Component: postgis Version: master
Keywords: Cc:

Description

Loading PostGIS into 'postgis_reg' 
  /var/lib/jenkins/workspace/postgis/branches/3.0/regress/00-regress-install/share/contrib/postgis/postgis.sql

  /var/lib/jenkins/workspace/postgis/branches/3.0/regress/00-regress-install/share/contrib/postgis/postgis_comments.sql

  /var/lib/jenkins/workspace/postgis/branches/3.0/regress/00-regress-install/share/contrib/postgis/postgis_proc_set_search_path.sql
PostgreSQL 12devel on x86_64-pc-linux-gnu, compiled by gcc (Debian 8.3.0-5) 8.3.0, 64-bit
  Postgis 3.0.0dev - r - 2019-04-14 04:22:36
  scripts 3.0.0dev r0
  GEOS: 3.8.0dev-CAPI-1.11.0 859dc941
  PROJ: Rel. 5.2.0, September 15th, 2018

 tickets .. failed (diff expected obtained: /var/lib/jenkins/workspace/postgis/tmp/3_0_pg12w64/test_98_diff)
-----------------------------------------------------------------------------
--- tickets_expected	2019-04-13 15:14:35.896524387 +0000
+++ /var/lib/jenkins/workspace/postgis/tmp/3_0_pg12w64/test_98_out	2019-04-14 04:25:24.595690005 +0000
@@ -303,7 +303,7 @@
 #3627b|t
 #3704|t
 #3709|t
-NOTICE:  Hole lies outside shell at or near point 25495368.044100001 6671726.9312000005
+NOTICE:  Hole lies outside shell at or near point nan nan
 #3719a|f
 #3719b|t
 #3774|t
-----------------------------------------------------------------------------

I had disabled raster builting to get this far. I suspect the sfcgal I installed brought in an old GDAL and the old GDAL brought in an old proj. So I uninstalled all that and ran without GDAL or SFCGAL.

I haven't checked on my local to see what errors I get (as I'm getting a bunch of raster erros at moment with proj).

But note though gitlab and github are showing greens, they are broken because of #4375

Change History (2)

comment:1 by robe, 6 years ago

Just tested on my local with proj 6.0.0 and no errors., but that doesn't rule out issue with proj 5.2 or that this is specific to pg12 head.

Note: See TracTickets for help on using tickets.