Opened 2 years ago
Closed 2 years ago
#5282 closed defect (fixed)
boundary, relate_bnr regression on GEOS 3.9.4
Reported by: | robe | Owned by: | robe |
---|---|---|---|
Priority: | blocker | Milestone: | PostGIS 2.5.9 |
Component: | postgis | Version: | 3.1.x |
Keywords: | Cc: |
Description
Debbie is showing this when testing PostGIS 3.1.8 against GEOS 3.9.4dev
https://debbie.postgis.net/job/PostGIS_Regress/23080/console
23:56:51 PostgreSQL 11.17 on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit 23:56:51 Postgis 3.1.8dev - (3.1.7-21-gfe5eb4f54) - 2022-11-06 03:52:59 23:56:51 scripts 3.1.8dev 3.1.7-21-gfe5eb4f54 23:56:51 raster scripts 3.1.8dev 3.1.7-21-gfe5eb4f54 23:56:51 GEOS: 3.9.4dev-CAPI-1.14.4 23:56:51 PROJ: 7.2.1 23:56:51 SFCGAL: 1.3.8 23:56:51 GDAL: GDAL 3.4.3, released 2022/04/22 23:56:51 ./regress/core/boundary .. failed (diff expected obtained: /var/lib/jenkins/workspace/postgis/tmp/3_1_pg11w64/test_4_diff) 23:56:51 ----------------------------------------------------------------------------- 23:56:51 --- ./regress/core/boundary_expected 2021-01-14 01:11:03.006011680 +0000 23:56:51 +++ /var/lib/jenkins/workspace/postgis/tmp/3_1_pg11w64/test_4_out 2022-11-06 03:56:51.939427452 +0000 23:56:51 @@ -1,5 +1,5 @@ 23:56:51 MULTIPOINT(1 1,-1 1) 23:56:51 LINESTRING(1 1,0 0,-1 1,1 1) 23:56:51 LINESTRING(1 1 1,0 0 1,-1 1 1,1 1 1) 23:56:51 -MULTIPOINT(-1 1 1,1 1 0.75) 23:56:51 +MULTIPOINT(-1 1 1,1 1 1) 23:56:51 LINESTRING(1 1,0 0,-1 1,1 1) 23:56:51 ----------------------------------------------------------------------------- 23:57:43 ./regress/core/relate_bnr .. failed (diff expected obtained: /var/lib/jenkins/workspace/postgis/tmp/3_1_pg11w64/test_89_diff) 23:57:44 ----------------------------------------------------------------------------- 23:57:44 --- ./regress/core/relate_bnr_expected 2021-01-14 01:11:03.070011681 +0000 23:57:44 +++ /var/lib/jenkins/workspace/postgis/tmp/3_1_pg11w64/test_89_out 2022-11-06 03:57:44.017813759 +0000 23:57:44 @@ -28,7 +28,7 @@ 23:57:44 28|10FF0FFF2|10FF0FFF2|1FFFFFFF2|10FF0FFF2 23:57:44 29|FF1FF0102|FF1FF0102|FF1FF0102|FF1FF0102 23:57:44 30|FF1FF0102|FF1FF0102|FF1FFF1F2|FF1FF0102 23:57:44 -31|FF1FF01F2|FF1FF01F2|FF1FF01F2|FF1FF01F2 23:57:44 +31|FF1FF01F2|FF1FF0102|FF1FF0102|FF1FF01F2 23:57:44 32|FF1FF01F2|FF1FF0102|FF1FFF1F2|FF1FF01F2 23:57:44 33|1FFF0FFF2|1FFF0FFF2|1FFFFFFF2|1FFF0FFF2 23:57:44 34|1FFF0FFF2|1FFF0FFF2|1FFFFFFF2|1FFF0FFF2 23:57:44 -----------------------------------------------------------------------------
My local GEOS is 3.9.2ish and doesn't show this and sadly winnie's geos 3.9 builds are broken so couldn't grab a newer binary from her to confirm.
I know we changed the behavior of relate_bnr, so that one I'll just take out the test as I did in master. The boundary one I don't recall but might be related.
Change History (8)
comment:1 by , 2 years ago
Milestone: | PostGIS 3.1.8 → PostGIS 3.0.8 |
---|
comment:2 by , 2 years ago
Owner: | changed from | to
---|
comment:3 by , 2 years ago
comment:6 by , 2 years ago
Milestone: | PostGIS 3.0.8 → PostGIS 2.5.9 |
---|
comment:8 by , 2 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
3.2 and 3.3 already had the relate_bnr tests taken out and the boundary tests are completely different.
Note:
See TracTickets
for help on using tickets.
In d624047c/git: