[PostGIS] #5683: 32bit test fails on ST_SnapToGrid test
PostGIS
trac at osgeo.org
Thu Mar 14 17:20:23 PDT 2024
#5683: 32bit test fails on ST_SnapToGrid test
----------------------+---------------------------
Reporter: strk | Owner: pramsey
Type: defect | Status: new
Priority: blocker | Milestone: PostGIS 3.5.0
Component: postgis | Version: master
Resolution: | Keywords: regression
----------------------+---------------------------
Comment (by robe):
apologies that thing I thought was a failure
is expected result and shows on stable-3.4 as well
{{{
Test: test_lwgeom_segmentize2d ...NOTICE:
/builds/postgis/postgis/liblwgeom/ptarray.c:449 - ptarray_segmentize2d:
Too many segments required (1.000000e+101)
}}}
But interestingly stable-3.4 32-bit gitlab run is not showing the
test_grid_in_place error.
That is passing with flying colors as is the rest of the tests
https://gitlab.com/postgis/postgis/-/jobs/6398823690#L733
I thought maybe it was the debian version, but master and stable-3.4 are
running debian bookworm
But I do notice the cu_misc.c grid tests change in master which I presume
pramsey added to exercise
what is causing the postgresql failures.
master has an extra test:
{{{
do_grid_test(
"LINESTRING(0 0,1 1,1 1,1 1)",
"LINESTRING(0 0,1 1)",
0.001
);
}}}
I'm going to add this to 3.4 as well to see if gitlab test32 is still a
happy camper.
--
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5683#comment:6>
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.
More information about the postgis-tickets
mailing list