[postgis-tickets] [PostGIS] #5406: Proj Regress failures on winnie 3.2 branch

[PostGIS]

#5406: Proj Regress failures on winnie 3.2 branch
-----------------------+---------------------------
 Reporter:  robe       |      Owner:  robe
     Type:  defect     |     Status:  new
 Priority:  medium     |  Milestone:  PostGIS 3.2.6
Component:  buildbots  |    Version:  3.3.x
 Keywords:             |
-----------------------+---------------------------
 Not sure when this started, but winnie is failing on 3.2 proj tests

 What I find especially interesting, is the proj tests themselves are fine


 {{{
 ./regress/core/regress_proj_basic .. ok in 418 ms
  ./regress/core/regress_proj_adhoc .. ok in 428 ms
  ./regress/core/regress_proj_cache_overflow .. ok in 1028 ms
  ./regress/core/regress_proj_4890 .. ok in 425 ms
 }}}



 But things like gml and raster gdalwarp stuff are not happy at all

 {{{
 PostgreSQL 14.8, compiled by Visual C++ build 1914, 64-bit
   Postgis 3.2.6dev - (3.2.5-4-g59a8f9d63) - 2023-06-19 18:57:21
   scripts 3.2.6dev 3.2.5-4-g59a8f9d63
   raster scripts 3.2.6dev 3.2.5-4-g59a8f9d63
   GEOS: 3.11.0-CAPI-1.17.0
   PROJ: 7.2.1
   SFCGAL: 1.4.1
   GDAL: GDAL 3.4.3, released 2022/04/22 GDAL_DATA not found

 -----------------------------------------------------------------------------

  ./regress/core/in_gml .. failed (diff expected obtained:
 /projects/postgis/tmp/3.2.5dev_pg14_geos3.11.0_gdal3.4.3w64/test_25_diff)
 -----------------------------------------------------------------------------
 --- ./regress/core/in_gml_expected      2022-02-12 19:34:12.520113300
 -0500
 +++
 /projects/postgis/tmp/3.2.5dev_pg14_geos3.11.0_gdal3.4.3w64/test_25_out
 2023-06-19 15:15:25.155035500 -0400
 @@ -95,7 +95,7 @@
  mpoint_4|MULTIPOINT EMPTY
  mpoint_5|MULTIPOINT EMPTY
  mpoint_6|MULTIPOINT(1 2,3 4)
 -mpoint_7|27582|MULTIPOINT(1 2,400000 7000000)
 +ERROR:  Could not create LWPROJ*
  mpoint_8|MULTIPOINT(1 2)
  mpoint_9|MULTIPOINT(1 2,3 4)
  mpoint_10|MULTIPOINT EMPTY
 @@ -107,7 +107,7 @@

 ./raster/test/regress/permitted_gdal_drivers .. ok in 512 ms
  ./raster/test/regress/tickets .. failed (diff expected obtained:
 /projects/postgis/tmp/3.2.5dev_pg14_geos3.11.0_gdal3.4.3w64/test_303_diff)
 -----------------------------------------------------------------------------
 --- ./raster/test/regress/tickets_expected      2022-02-12
 19:34:11.858928700 -0500
 +++
 /projects/postgis/tmp/3.2.5dev_pg14_geos3.11.0_gdal3.4.3w64/test_303_out
 2023-06-19 15:26:45.578607000 -0400
 @@ -2,7 +2,7 @@
  #2532.1|
  #2532.2|
  NOTICE:  Raster has default geotransform. Adjusting metadata for use of
 GDAL Warp API
 -#2911|0|0|5|5|2|-2|0|0|0|1
 +ERROR:  rt_util_gdal_convert_sr: Could not process the provided srs:
 EPSG:32731
  t
  test_raster_scale_regular|rast||1
  ERROR:  new row for relation "test_raster_scale_regular" violates check
 constraint "enforce_scaley_rast"

 }}}

 I'm assuming it some sort of misconfiguration I have here
-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5406>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.