Opened 5 years ago
Closed 4 years ago
#4559 closed defect (fixed)
[raster] PG 13 / GDAL 3.1: rt_gdalwarp regress failing
| Reported by: | Algunenano | Owned by: | Bborie Park |
|---|---|---|---|
| Priority: | medium | Milestone: | PostGIS 3.1.0 |
| Component: | raster | Version: | master |
| Keywords: | Cc: |
Description
Ther are a bunch of new notices in raster related to SRID values over SRID_MAXIMUM:
rt_gdalwarp .. failed (diff expected obtained: /tmp/pgis_reg/test_52_diff) ----------------------------------------------------------------------------- --- rt_gdalwarp_expected 2019-10-25 13:40:29.000000000 +0000 +++ /tmp/pgis_reg/test_52_out 2019-10-25 13:46:31.848481999 +0000 @@ -7,27 +7,153 @@ NOTICE: Raster has default geotransform. Adjusting metadata for use of GDAL Warp API NOTICE: Values must be provided for both X and Y when specifying the scale. Returning original raster NOTICE: Values must be provided for both X and Y when specifying the scale. Returning original raster +NOTICE: SRID value 2139062143 > SRID_MAXIMUM converted to 999346 +NOTICE: SRID value 2139062143 > SRID_MAXIMUM converted to 999346 +NOTICE: SRID value 2139062143 > SRID_MAXIMUM converted to 999346 +NOTICE: SRID value 2139062143 > SRID_MAXIMUM converted to 999346 +NOTICE: SRID value 2139062143 > SRID_MAXIMUM converted to 999346
There are other failures too:
-1.10|993310|141|87|1|1000.000|-1000.000|0.000|0.000|-175453.086|114987.661|32BF|0.000|t|1.000|1.000| +1.10|128|0|0|1|1000.000|0.000|0.000|1000.000|0.000|0.000|32BF|0.000|t|1.000|1.000|
Build example: https://travis-ci.org/postgis/postgis/jobs/602060439
Change History (5)
comment:1 by , 4 years ago
comment:2 by , 4 years ago
I'm seeing it on debbie's dev runs for PG 13, this is with
https://debbie.postgis.net/view/PostgreSQL/job/PostGIS_Regress_PGDEV_Weekly/10546/console
-------------- Compiler Info ------------- C compiler: gcc -std=gnu99 -g -O2 -fno-math-errno -fno-signed-zeros C++ compiler (Wagyu): gcc -std=c++11 -x c++ CPPFLAGS: -I/var/lib/jenkins/workspace/geos/rel-3.8w64/include -I/usr/include/libxml2 -I/usr/include -I/usr/include/json-c LDFLAGS: -lm SQL preprocessor: /usr/bin/cpp -traditional-cpp -w -P -------------- Additional Info ------------- Interrupt Tests: DISABLED use: --with-interrupt-tests to enable -------------- Dependencies -------------- GEOS config: /var/lib/jenkins/workspace/geos/rel-3.8w64/bin/geos-config GEOS version: 3.9.0dev GDAL config: /var/lib/jenkins/workspace/gdal/rel-2.4w64/bin/gdal-config GDAL version: 2.4.3 SFCGAL config: /usr/bin/sfcgal-config SFCGAL version: 1.3.7 PostgreSQL config: /var/lib/jenkins/workspace/pg/rel/pg13w64/bin/pg_config PostgreSQL version: PostgreSQL 13devel PROJ4 version: 62 Libxml2 config: /usr/bin/xml2-config Libxml2 version: 2.9.4 JSON-C support: yes protobuf support: yes protobuf-c version: 1003002 PCRE support: no Perl: /usr/bin/perl Wagyu: yes --------------- Extensions --------------- PostGIS Raster: enabled PostGIS Topology: enabled SFCGAL support: enabled Address Standardizer support: disabled -------- Documentation Generation -------- xsltproc: /usr/bin/xsltproc xsl style sheets: /usr/share/xml/docbook/stylesheet/docbook-xsl dblatex: /usr/bin/dblatex convert: /usr/bin/convert mathml2.dtd: /usr/share/xml/schema/w3c/mathml/dtd/mathml2.dtd
rt_gdalwarp .. failed (diff expected obtained: /var/lib/jenkins/workspace/postgis/regress_pgdev/branches/3.1/tmp/3_1_pg13w64/test_52_diff) ----------------------------------------------------------------------------- --- rt_gdalwarp_expected 2019-10-28 21:42:58.098356962 +0000 +++ /var/lib/jenkins/workspace/postgis/regress_pgdev/branches/3.1/tmp/3_1_pg13w64/test_52_out 2019-10-28 21:50:33.970353820 +0000 @@ -7,27 +7,48 @@ NOTICE: Raster has default geotransform. Adjusting metadata for use of GDAL Warp API NOTICE: Values must be provided for both X and Y when specifying the scale. Returning original raster NOTICE: Values must be provided for both X and Y when specifying the scale. Returning original raster +NOTICE: SRID value 2139062143 > SRID_MAXIMUM converted to 999346 +NOTICE: SRID value 2139062143 > SRID_MAXIMUM converted to 999346 +NOTICE: SRID value 2139062143 > SRID_MAXIMUM converted to 999346 +NOTICE: SRID value 2139062143 > SRID_MAXIMUM converted to 999346 +NOTICE: SRID value 2139062143 > SRID_MAXIMUM converted to 999346 +NOTICE: SRID value 2139062143 > SRID_MAXIMUM converted to 999346 +NOTICE: SRID value 2139062143 > SRID_MAXIMUM converted to 999346 +NOTICE: SRID value 2139062143 > SRID_MAXIMUM converted to 999346 +NOTICE: SRID value 2139062143 > SRID_MAXIMUM converted to 999346 +NOTICE: SRID value 2139062143 > SRID_MAXIMUM converted to 999346 +NOTICE: SRID value 2139062143 > SRID_MAXIMUM converted to 999346 +NOTICE: SRID value 2139062143 > SRID_MAXIMUM converted to 999346 +NOTICE: SRID value 2139062143 > SRID_MAXIMUM converted to 999346 +NOTICE: SRID value 2139062143 > SRID_MAXIMUM converted to 999346 +NOTICE: SRID value 2139062143 > SRID_MAXIMUM converted to 999346 +NOTICE: SRID value 2139062143 > SRID_MAXIMUM converted to 999346 +NOTICE: SRID value 2139062143 > SRID_MAXIMUM converted to 999346 +NOTICE: SRID value 2139062143 > SRID_MAXIMUM converted to 999346 +NOTICE: SRID value 2139062143 > SRID_MAXIMUM converted to 999346 +NOTICE: SRID value 2139062143 > SRID_MAXIMUM converted to 999346 +NOTICE: SRID value 2139062143 > SRID_MAXIMUM converted to 999346 0.0||||||||||||| 0.1|993310|12|12|1|1009.894|-1009.894|0.000|0.000|950732.188|1409281.783|t|t|t 0.10|992163|10|10|1|1000.000|-1000.000|0.000|0.000|-500000.000|600000.000|t|t|t 0.11|992163|11|10|1|1000.000|-1000.000|0.000|0.000|-500001.000|600000.000|t|t|t 0.12|992163|10|11|1|1000.000|-1000.000|0.000|0.000|-500000.000|600009.000|t|t|t 0.13|992163|11|11|1|1000.000|-1000.000|0.000|0.000|-500100.000|600950.000|t|t|t -0.14|992163|201|201|1|50.000|50.000|0.000|0.000|-500040.000|589957.000|t|t|t
comment:3 by , 4 years ago
wow we are already testing PostgreSQL 13. This only happens in 13?
As far as I can see, yes.
I'm seeing it on debbie's dev runs for PG 13, this is with
I was going to say that this might discard GDAL as responsible, but I see that Debbie is running 2.4/HEAD so it can either be some change applied in GDAL master and backported or a change in PG13.
comment:4 by , 4 years ago
I've updated my local gdal to master and it passes the tests:
------------ Dependencies -------------- GEOS config: /usr/bin/geos-config GEOS version: 3.9.0dev GDAL config: /usr/bin/gdal-config GDAL version: 3.1.0 SFCGAL config: /usr/bin/sfcgal-config SFCGAL version: 1.3.7 PostgreSQL config: /usr/bin/pg_config PostgreSQL version: PostgreSQL 12.0 PROJ4 version: 62 Libxml2 config: /usr/bin/xml2-config Libxml2 version: 2.9.9 JSON-C support: yes protobuf support: yes protobuf-c version: 1003002 PCRE support: yes Perl: /usr/bin/perl Wagyu: yes
So it looks like something related to PG13.
comment:5 by , 4 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
I've added pg13 to master regular run, seems to have regressed fine, so closing this out.
https://debbie.postgis.net/job/PostGIS_Regress/13906/consoleFull
Note:
See TracTickets
for help on using tickets.
wow we are already testing PostgreSQL 13. This only happens in 13?