#5605 closed defect (fixed)
regress/core/regress_buffer_params failed with latest geos e4a6e1af65f7d60fa63d7666f6cb000
Reported by: | ImreSamu | Owned by: | pramsey |
---|---|---|---|
Priority: | medium | Milestone: | PostGIS 3.3.5 |
Component: | postgis | Version: | 3.4.x |
Keywords: | geos, regress, regress_buffer_params | Cc: | ImreSamu |
Description (last modified by )
With the last Geos changes the regress_buffer_params
failing;
regress/core/regress_buffer_params .. failed (diff expected obtained: /tmp/pgis_reg/test_51_diff)
IMHO: the root cause is this GEOS commit:
ARG PGIS1_GEOS_CHECKOUT_SHA1=e4a6e1af65f7d60fa63d7666f6cb000e365bb50f
https://github.com/libgeos/geos/commit/e4a6e1af65f7d60fa63d7666f6cb000e365bb50f
With this GEOS commit, it is OK:
ARG PGIS1_GEOS_CHECKOUT_SHA1=bb2db233eb2d51ba1f44cfaaf5dbd39f0cb1af87
context ( first detection )
- updating the new(development) '16-master-bookworm'
- CI: https://github.com/ImreSamu/docker-postgis/actions/runs/6803399664/job/18498652762
- original commit, first detection: https://github.com/ImreSamu/docker-postgis/commit/32eeb6f20e999857fbc806834c28fd111052a7bd
- test Dockerfile: https://github.com/ImreSamu/docker-postgis/blob/32eeb6f/16-master/bookworm/Dockerfile
Change History (11)
comment:1 by , 14 months ago
Description: | modified (diff) |
---|
comment:2 by , 14 months ago
follow-up: 4 comment:3 by , 14 months ago
Yes, change the test. This is due to an improvement in buffer vertex generation to avoid tiny numbers near zero.
Can you simply add a small tolerance to check vertex equality?
follow-up: 6 comment:4 by , 14 months ago
Replying to mdavis:
Yes, change the test. This is due to an improvement in buffer vertex generation to avoid tiny numbers near zero.
Can you simply add a small tolerance to check vertex equality?
vertex equality? Wouldn't that make it still fail. Was going to round and normalize
comment:5 by , 14 months ago
Doing this now, looks like others on this test have been snapped or normalized in the past. I'm tempted to do that for all of them on this test to future proof this.
comment:7 by , 14 months ago
Looks like pramsey bit me too it, but his description is wrong and he only dealt with the single one. I'm going to push my revision shortly
comment:10 by , 13 months ago
Milestone: | PostGIS 3.4.1 → PostGIS 3.3.5 |
---|
Similar failure on debbie, berrie, and berrie64
Though the difference seems to be fairly harmless a 0 vs. a 2.449e-16. Maybe we should just change this test