Ubuntu
postgis package

FTBFS in Jammy - 4348ReversedSmall

Bug #1952604 reported by Christian Ehrhardt 
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
postgis (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

FTBFS on ppc64 as synced over from Debian
=> https://launchpad.net/ubuntu/+source/postgis/3.1.4+dfsg-3build1

Failing log:
https://launchpadlibrarian.net/569861170/buildlog_ubuntu-jammy-ppc64el.postgis_3.1.4+dfsg-3build1_BUILDING.txt.gz

The same built fine in Debian
=> https://buildd.debian.org/status/fetch.php?pkg=postgis&arch=ppc64el&ver=3.1.4%2Bdfsg-3%2Bb1&stamp=1634938635&raw=0

Error:

./regress/core/mvt .. failed (diff expected obtained: /tmp/pgis_reg/test_110_diff)
-----------------------------------------------------------------------------
--- ./regress/core/mvt_expected 2021-09-04 05:03:43.000000000 +0000
+++ /tmp/pgis_reg/test_110_out 2021-11-20 06:56:10.856917815 +0000
@@ -138,7 +138,7 @@
 #4348Clip|t
 #4348Invalid|t
 #4348Dropped|t
-#4348ReversedSmall|t
+#4348ReversedSmall|
 #4348Reversed2|t
 #4348Point|t
 #4348Crash|t
-----------------------------------------------------------------------------

Later there is a test log detail:

Failed: 1
make[2]: *** [regress/runtest.mk:10: check-regress] Error 1
make[2]: Leaving directory '/<<BUILDDIR>>/postgis-3.1.4+dfsg'
*** /tmp/pg_virtualenv.DM9fVH/log/postgresql-14-regress.log (last 100 lines) ***
  ST_Grayscale(rast)
 FROM raster_grayscale_in
 ORDER BY rid
 LIMIT 1;
2021-11-20 06:57:01.875 UTC [28528] buildd@postgis_reg ERROR: Band at index '2' not found for raster '2'
2021-11-20 06:57:01.875 UTC [28528] buildd@postgis_reg CONTEXT: PL/pgSQL function st_grayscale(rastbandarg[],text) line 41 at RAISE
2021-11-20 06:57:01.875 UTC [28528] buildd@postgis_reg STATEMENT: SELECT
  ST_Grayscale(
   ARRAY[
    ROW(rast, 1)::rastbandarg,
    ROW(rast, 2)::rastbandarg,
    ROW(rast, 1)::rastbandarg
   ]::rastbandarg[]
  )
 FROM raster_grayscale_in
 ORDER BY rid
 LIMIT 1;
ORC error: No callback manager available for powerpc64le-unknown-linux-gnu
ORC error: No callback manager available for powerpc64le-unknown-linux-gnu
ORC error: No callback manager available for powerpc64le-unknown-linux-gnu
ORC error: No callback manager available for powerpc64le-unknown-linux-gnu
2021-11-20 06:57:03.210 UTC [28576] buildd@postgis_reg ERROR: Tolerance cannot be less than zero

2021-11-20 06:57:03.210 UTC [28576] buildd@postgis_reg STATEMENT: SELECT
  '2.2',
  r1.rid,
  r2.rid,
  -1 AS distance,
  ST_DWithin(r1.rast, NULL, r2.rast, NULL, -1)
 FROM raster_geos_rast r1
 CROSS JOIN raster_geos_rast r2
 WHERE r1.rid = 0;
2021-11-20 06:57:03.216 UTC [28576] buildd@postgis_reg ERROR: Tolerance cannot be less than zero

2021-11-20 06:57:03.216 UTC [28576] buildd@postgis_reg STATEMENT: SELECT
  '2.4',
  r1.rid,
  r2.rid,
  -1 AS distance,
  ST_DFullyWithin(r1.rast, NULL, r2.rast, NULL, -1)
 FROM raster_geos_rast r1
 CROSS JOIN raster_geos_rast r2
 WHERE r1.rid = 0;
ORC error: No callback manager available for powerpc64le-unknown-linux-gnu
ORC error: No callback manager available for powerpc64le-unknown-linux-gnu
ERROR 4: `/vsimem/in.dat' not recognized as a supported file format.
2021-11-20 06:57:04.606 UTC [28612] buildd@postgis_reg ERROR: RASTER_fromGDALRaster: Could not open bytea with GDAL. Check that the bytea is of a GDAL supported format
2021-11-20 06:57:04.606 UTC [28612] buildd@postgis_reg STATEMENT: SELECT convert_from(ST_AsGDALRaster(ST_FromGDALRaster('<VRTDataset rasterXSize="1000"
 rasterYSize="1"><VRTRasterBand band="1"
 subClass="VRTRawRasterBand"><SourceFilename>/etc/passwd</SourceFilename></VRTRasterBand></VRTDataset>'::bytea),
 'EHDR')::bytea, 'LATIN1');
ERROR 4: <VRTDataset rasterXSize="1000" rasterYSize="1"><VRTRasterBand band="1" subClass="VRTRawRasterBand"><SourceFilename>/etc/passwd</SourceFilename></VRTRasterBand></VRTDataset>: No such file or directory
2021-11-20 06:57:04.609 UTC [28612] buildd@postgis_reg ERROR: rt_band_load_offline_data: Cannot open offline raster: <VRTDataset rasterXSize="1000" rasterYSize="1"><VRTRasterBand band="1" subClass="VRTRawRasterBand"><SourceFilename>/etc/passwd</SourceFilename></VRTRasterBand></VRTDataset>
2021-11-20 06:57:04.609 UTC [28612] buildd@postgis_reg STATEMENT: SELECT count(convert_from(ST_AsGDALRaster(r, 'EHDR')::bytea, 'LATIN1')) as passwd from raster_test where lbl = 'passwd';
ERROR 4: <VRTDataset rasterXSize="1000" rasterYSize="1"><VRTRasterBand band="1" subClass="VRTRawRasterBand"><SourceFilename>/etc/passwd</SourceFilename></VRTRasterBand></VRTDataset>: No such file or directory
2021-11-20 06:57:04.610 UTC [28612] buildd@postgis_reg ERROR: rt_band_load_offline_data: Cannot open offline raster: <VRTDataset rasterXSize="1000" rasterYSize="1"><VRTRasterBand band="1" subClass="VRTRawRasterBand"><SourceFilename>/etc/passwd</SourceFilename></VRTRasterBand></VRTDataset>
2021-11-20 06:57:04.610 UTC [28612] buildd@postgis_reg STATEMENT: SELECT count(convert_from(ST_AsGDALRaster(r, 'EHDR')::bytea, 'LATIN1')) as passwd from raster_test where lbl = 'passwd';
ERROR 4: <VRTDataset rasterXSize="1000" rasterYSize="1"><VRTRasterBand band="1" subClass="VRTRawRasterBand"><SourceFilename>/etc/passwd</SourceFilename></VRTRasterBand></VRTDataset>: No such file or directory
2021-11-20 06:57:04.616 UTC [28612] buildd@postgis_reg ERROR: rt_band_load_offline_data: Cannot open offline raster: <VRTDataset rasterXSize="1000" rasterYSize="1"><VRTRasterBand band="1" subClass="VRTRawRasterBand"><SourceFilename>/etc/passwd</SourceFilename></VRTRasterBand></VRTDataset>
2021-11-20 06:57:04.616 UTC [28612] buildd@postgis_reg STATEMENT: SELECT count(convert_from(ST_AsGDALRaster(r, 'EHDR')::bytea, 'LATIN1')) as passwd from raster_test where lbl = 'passwd';
ERROR 4: <VRTDataset rasterXSize="1000" rasterYSize="1"><VRTRasterBand band="1" subClass="VRTRawRasterBand"><SourceFilename>/etc/passwd</SourceFilename></VRTRasterBand></VRTDataset>: No such file or directory
2021-11-20 06:57:04.616 UTC [28612] buildd@postgis_reg ERROR: rt_band_load_offline_data: Cannot open offline raster: <VRTDataset rasterXSize="1000" rasterYSize="1"><VRTRasterBand band="1" subClass="VRTRawRasterBand"><SourceFilename>/etc/passwd</SourceFilename></VRTRasterBand></VRTDataset>
2021-11-20 06:57:04.616 UTC [28612] buildd@postgis_reg STATEMENT: SELECT count(convert_from(ST_AsGDALRaster(r, 'EHDR')::bytea, 'LATIN1')) as passwd from raster_test where lbl = 'passwd';
2021-11-20 06:57:04.804 UTC [28624] buildd@postgis_reg WARNING: Unable to add constraint: 'scale_x'. Skipping
2021-11-20 06:57:04.804 UTC [28624] buildd@postgis_reg CONTEXT: PL/pgSQL function addrasterconstraints(name,name,name,text[]) line 113 at RAISE
2021-11-20 06:57:04.807 UTC [28624] buildd@postgis_reg ERROR: new row for relation "test_raster_scale_regular" violates check constraint "enforce_scaley_rast"
2021-11-20 06:57:04.807 UTC [28624] buildd@postgis_reg DETAIL: Failing row contains (3, 01000001006ABC74931804F03FCB1A50CAFFFFEF3F0000000000000000000000...).
2021-11-20 06:57:04.807 UTC [28624] buildd@postgis_reg CONTEXT: SQL statement "INSERT INTO test_raster_scale_regular VALUES ('3', '01000001006ABC74931804F03FCB1A50CAFFFFEF3F00000000000000000000000000000000000000000000000000000000000000000000000002000200440001010101')"
 PL/pgSQL function make_test_raster(text,integer,double precision,double precision) line 16 at EXECUTE
2021-11-20 06:57:04.807 UTC [28624] buildd@postgis_reg STATEMENT: SELECT make_test_raster('regular', 3, 1.001, 0.9999999);
2021-11-20 06:57:04.811 UTC [28624] buildd@postgis_reg ERROR: new row for relation "test_raster_scale_big" violates check constraint "enforce_scalex_rast"
2021-11-20 06:57:04.811 UTC [28624] buildd@postgis_reg DETAIL: Failing row contains (1, 0100000100E1639D31956AE5C3000000000000F03F0000000000000000000000...).
2021-11-20 06:57:04.811 UTC [28624] buildd@postgis_reg CONTEXT: SQL statement "INSERT INTO test_raster_scale_big VALUES ('1', '0100000100E1639D31956AE5C3000000000000F03F00000000000000000000000000000000000000000000000000000000000000000000000002000200440001010101')"
 PL/pgSQL function make_test_raster(text,integer,double precision,double precision) line 16 at EXECUTE
2021-11-20 06:57:04.811 UTC [28624] buildd@postgis_reg STATEMENT: SELECT make_test_raster('big', 1, -12345678901234567890.0);
2021-11-20 06:57:04.813 UTC [28624] buildd@postgis_reg WARNING: Unable to add constraint: 'scale_x'. Skipping
2021-11-20 06:57:04.813 UTC [28624] buildd@postgis_reg CONTEXT: PL/pgSQL function addrasterconstraints(name,name,name,text[]) line 113 at RAISE
2021-11-20 06:57:04.816 UTC [28624] buildd@postgis_reg ERROR: new row for relation "test_raster_scale_small" violates check constraint "enforce_scaley_rast"
2021-11-20 06:57:04.816 UTC [28624] buildd@postgis_reg DETAIL: Failing row contains (3, 0100000100F168E388B5F8E43E72C45A7C0A00F03F0000000000000000000000...).
2021-11-20 06:57:04.816 UTC [28624] buildd@postgis_reg CONTEXT: SQL statement "INSERT INTO test_raster_scale_small VALUES ('3', '0100000100F168E388B5F8E43E72C45A7C0A00F03F00000000000000000000000000000000000000000000000000000000000000000000000002000200440001010101')"
 PL/pgSQL function make_test_raster(text,integer,double precision,double precision) line 16 at EXECUTE
2021-11-20 06:57:04.816 UTC [28624] buildd@postgis_reg STATEMENT: SELECT make_test_raster('small', 3, 0.00001, 1.00001);
2021-11-20 06:57:04.841 UTC [28624] buildd@postgis_reg WARNING: Unable to add constraint: 'blocksize_x'. Skipping
2021-11-20 06:57:04.841 UTC [28624] buildd@postgis_reg CONTEXT: PL/pgSQL function addrasterconstraints(name,name,name,text[]) line 113 at RAISE
 PL/pgSQL function addrasterconstraints(name,name,name,boolean,boolean,boolean,boolean,boolean,boolean,boolean,boolean,boolean,boolean,boolean,boolean) line 53 at RETURN
2021-11-20 06:57:04.841 UTC [28624] buildd@postgis_reg WARNING: Unable to add constraint: 'blocksize_y'. Skipping
2021-11-20 06:57:04.841 UTC [28624] buildd@postgis_reg CONTEXT: PL/pgSQL function addrasterconstraints(name,name,name,text[]) line 113 at RAISE
 PL/pgSQL function addrasterconstraints(name,name,name,boolean,boolean,boolean,boolean,boolean,boolean,boolean,boolean,boolean,boolean,boolean,boolean) line 53 at RETURN
2021-11-20 06:57:04.841 UTC [28624] buildd@postgis_reg WARNING: Unable to add constraint: 'pixel_types'. Skipping
2021-11-20 06:57:04.841 UTC [28624] buildd@postgis_reg CONTEXT: PL/pgSQL function addrasterconstraints(name,name,name,text[]) line 113 at RAISE
 PL/pgSQL function addrasterconstraints(name,name,name,boolean,boolean,boolean,boolean,boolean,boolean,boolean,boolean,boolean,boolean,boolean,boolean) line 53 at RETURN
2021-11-20 06:57:04.841 UTC [28624] buildd@postgis_reg WARNING: Unable to add constraint: 'nodata_values'. Skipping
2021-11-20 06:57:04.841 UTC [28624] buildd@postgis_reg CONTEXT: PL/pgSQL function addrasterconstraints(name,name,name,text[]) line 113 at RAISE
 PL/pgSQL function addrasterconstraints(name,name,name,boolean,boolean,boolean,boolean,boolean,boolean,boolean,boolean,boolean,boolean,boolean,boolean) line 53 at RETURN
2021-11-20 06:57:04.841 UTC [28624] buildd@postgis_reg WARNING: Unable to add constraint: 'out_db'. Skipping
2021-11-20 06:57:04.841 UTC [28624] buildd@postgis_reg CONTEXT: PL/pgSQL function addrasterconstraints(name,name,name,text[]) line 113 at RAISE
 PL/pgSQL function addrasterconstraints(name,name,name,boolean,boolean,boolean,boolean,boolean,boolean,boolean,boolean,boolean,boolean,boolean,boolean) line 53 at RETURN
2021-11-20 06:57:04.842 UTC [28624] buildd@postgis_reg WARNING: Unable to add constraint: 'extent'. Skipping
2021-11-20 06:57:04.842 UTC [28624] buildd@postgis_reg CONTEXT: PL/pgSQL function addrasterconstraints(name,name,name,text[]) line 113 at RAISE
 PL/pgSQL function addrasterconstraints(name,name,name,boolean,boolean,boolean,boolean,boolean,boolean,boolean,boolean,boolean,boolean,boolean,boolean) line 53 at RETURN
Dropping cluster 14/regress ...

The test log lists important components:

The run in Debian had
PostgreSQL 14.0 (Debian 14.0-1) on powerpc64le-unknown-linux-gnu, compiled by gcc (Debian 10.3.0-11) 10.3.0, 64-bit
  Postgis 3.1.4 - (ded6c34) - 2021-10-22 21:28:51
  scripts 3.1.4 ded6c34
  raster scripts 3.1.4 ded6c34
  GEOS: 3.10.0-CAPI-1.16.0
  PROJ: 8.1.1
  SFCGAL: 1.4.0
  GDAL: GDAL 3.3.2, released 2021/09/01

Ubuntu had
PostgreSQL 14.1 (Ubuntu 14.1-1) on powerpc64le-unknown-linux-gnu, compiled by gcc (Ubuntu 11.2.0-10ubuntu1) 11.2.0, 64-bit
  Postgis 3.1.4 - (ded6c34) - 2021-10-28 06:20:59
  scripts 3.1.4 ded6c34
  raster scripts 3.1.4 ded6c34
  GEOS: 3.10.1-CAPI-1.16.0
  PROJ: 8.2.0
  SFCGAL: 1.4.0
  GDAL: GDAL 3.3.3, released 2021/10/25

Note: Another Ubuntu build failed before 14.1 with 14.0, only GDAL (or
anything not listed here) is new.

Note:
There is 3.2.0~beta1+dfsg-1~exp1 in debian/experimental but it didn't have an
obvious change/fix in git for this, might still be worth to PPA build 3.2 in
an Ubuntu Jammy PPA.

Repro:
1. build last good one 3.1.1+dfsg-1 in Impish and Jammy on ppc64
2. build bad one 3.1.4+dfsg-3build1 in Impish and Jammy on ppc64

=> Unfortunately None of the above reproduces the issue on ppc64 in LXD
containers :-/ Not even the 4.1.4@Jammy which is continuously failing on
launchpad build retries (4/4 failing)

More logs (for patterns in them):
https://launchpadlibrarian.net/571347323/buildlog_ubuntu-jammy-ppc64el.postgis_3.1.4+dfsg-3build1_BUILDING.txt.gz
https://launchpadlibrarian.net/570874201/buildlog_ubuntu-jammy-ppc64el.postgis_3.1.4+dfsg-3build1_BUILDING.txt.gz
https://launchpadlibrarian.net/569861170/buildlog_ubuntu-jammy-ppc64el.postgis_3.1.4+dfsg-3build1_BUILDING.txt.gz

Related branches

~paelzer/ubuntu/+source/postgis:lp-1952604-ppc-test-skip
Sergio Durigan Junior (community): Approve
Canonical Server: Pending requested
Christian Ehrhardt : Pending requested
Diff: 61 lines (+13/-4)
4 files modified
debian/changelog (+7/-0)
debian/control (+2/-1)
debian/control.in (+2/-1)
debian/rules (+2/-2)
Christian Ehrhardt  (paelzer)
tags: added: update-excuse
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Tests are ignored on almost all architectures already

ifneq (,$(filter $(DEB_BUILD_ARCH),mips mips64el mipsel s390x alpha hppa hurd-i386 kfreebsd-i386 powerpc ppc64 sparc64))

e.g. s390x

./regress/core/mvt .. failed (diff expected obtained: /tmp/pgis_reg/test_110_diff)
-----------------------------------------------------------------------------
--- ./regress/core/mvt_expected 2021-09-04 05:03:43.000000000 +0000
+++ /tmp/pgis_reg/test_110_out 2021-10-28 06:40:17.858553302 +0000
@@ -105,10 +105,10 @@
 AEAogCB4Ag==
 TA13|GiUKBHRlc3QSDBICAAAYASIECTLePxoCYzEaAmMyIgIoASiAIHgC
 TA14|GpACCgR0ZXN0Ei8SAgAAGAIiJwny6wyShoMFOqUstRbBKYoPr5UBjxSFPpRS4XTkF/8lsE/8VZK5
-ARoKb3RoZXJfZ2VvbSLFAQrCATAxMDMwMDAwMjAxMTBGMDAwMDAxMDAwMDAwMDUwMDAwMDBEOTQw
-REZCQUZEOUVGMjQwNDc0RDYyNzJBODE2NTQ0MUQ5NDBERkJBRkQ5RUYyNDBDN0YzM0NBNkQ0MkQ1
-NDQxNkExQTNGOEQzQ0IwRjk0MEM3RjMzQ0E2RDQyRDU0NDE2QTFBM0Y4RDNDQjBGOTQwNDc0RDYy
-NzJBODE2NTQ0MUQ5NDBERkJBRkQ5RUYyNDA0NzRENjI3MkE4MTY1NDQxKIAgeAI=
+ARoKb3RoZXJfZ2VvbSLFAQrCATAwMjAwMDAwMDMwMDAwMEYxMTAwMDAwMDAxMDAwMDAwMDU0MEYy
+OUVGREJBREY0MEQ5NDE1NDE2QTg3MjYyNEQ0NzQwRjI5RUZEQkFERjQwRDk0MTU0MkRENEE2M0NG
+M0M3NDBGOUIwM0M4RDNGMUE2QTQxNTQyREQ0QTYzQ0YzQzc0MEY5QjAzQzhEM0YxQTZBNDE1NDE2
+QTg3MjYyNEQ0NzQwRjI5RUZEQkFERjQwRDk0MTU0MTZBODcyNjI0RDQ3KIAgeAI=
 TA15|GkkKBHRlc3QSEBIGAAABAQIAGAEiBAky3j8aAmMxGgJjMhoHY3N0cmluZyIDCgExIhQKEjEyLjIz
 MjM4OTI4MzIyMzIzOSiAIHgC
 D1|Gi8KBHRlc3QSDhIEAAABARgBIgQJMt4/GgJjMRoCYzIiAigBIgYKBGFiY2QogCB4Ag==
@@ -142,6 +142,6 @@
 #4348Reversed2|t
 #4348Point|t
 #4348Crash|t
-#4399|ST_AsMVTGeom|011100000001000000040000000000000000000000000000000000B0400000000000000000000000000000AF400000000000006040000000000000AF400000000000000000000000000000B040
-#4399|ST_AsMVTGeom|011100000001000000040000000000000000000000000000000000B0400000000000000000000000000000AF400000000000006040000000000000AF400000000000000000000000000000B040
+#4399|ST_AsMVTGeom|00000000110000000100000004000000000000000040B0000000000000000000000000000040AF000000000000406000000000000040AF000000000000000000000000000040B0000000000000
+#4399|ST_AsMVTGeom|00000000110000000100000004000000000000000040B0000000000000000000000000000040AF000000000000406000000000000040AF000000000000000000000000000040B0000000000000
 #4399|ST_AsMVTGeom|

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Discussed in IRC and then reported upstream https://trac.osgeo.org/postgis/ticket/5030#ticket

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

There is no movement upstream on this that would make a real fix achievable near term.

I thought about sending the change to Debian, but since they are not affected and 3.2 is around the corner (where things could be much different for everyone again) this makes not much sense right now.

Instead just disable this as Ubuntu Delta and reconsider submitting it if it remains in 3.2 and/or becomes a problem in Debian.

PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4728/+packages
MP: https://code.launchpad.net/~paelzer/ubuntu/+source/postgis/+git/postgis/+merge/412640

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Approved and uploaded

Uploading to ubuntu (via ftp to upload.ubuntu.com):
  Uploading postgis_3.1.4+dfsg-3ubuntu1.dsc: done.
  Uploading postgis_3.1.4+dfsg-3ubuntu1.debian.tar.xz: done.
  Uploading postgis_3.1.4+dfsg-3ubuntu1_source.buildinfo: done.
  Uploading postgis_3.1.4+dfsg-3ubuntu1_source.changes: done.
Successfully uploaded packages.

Changed in postgis (Ubuntu):
status: New → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package postgis - 3.1.4+dfsg-3ubuntu2

---------------
postgis (3.1.4+dfsg-3ubuntu2) jammy; urgency=medium

  * No-change rebuild against libgdal30

 -- Steve Langasek <email address hidden> Thu, 09 Dec 2021 00:31:45 +0000

Changed in postgis (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.