Opened 8 months ago

Last modified 8 weeks ago

#5636 new defect

berrie 32bit failing on garden tests on ST_MakePolygon

Reported by: robe Owned by: robe
Priority: medium Milestone: Website Management, Bots
Component: QA/buildbots Version: master
Keywords: Cc:

Description

This one I need to rerun. berrie64 is still doing garden testing and I think has gone passed this test Given this is several minors behind probably not much of a concern. I'll up to pg16 and rebuild pg15 to see if issue still continues

-------------- Dependencies -------------- 
17:13:42   GEOS config:          /home/jenkins/workspace/geos/rel-3.13.0/bin/geos-config
17:13:42   GEOS version:         3.13.0dev
17:13:42   GDAL config:          /usr/bin/gdal-config
17:13:42   GDAL version:         3.2.2
17:13:42   PostgreSQL config:    /home/jenkins/workspace/pg/label/berrie/rel/pg15w32/bin/pg_config
17:13:42   PostgreSQL version:   PostgreSQL 15.0
17:13:42   PROJ4 version:        72
17:13:42   Libxml2 config:       /usr/bin/xml2-config
17:13:42   Libxml2 version:      2.9.10
17:13:42   JSON-C support:       yes
17:13:42   protobuf support:     no
17:13:42   PCRE support:         Version 1
17:13:42   Perl:                 /usr/bin/perl
17:13:42 
SELECT ST_MakePolygon(foo1.the_geom,
                                                ARRAY[foo2.the_geom]
                                        ) As result, ST_AsText(foo1.the_geom) As ref1_geom, ST_AsText(foo2.the_geom) As ref2_geom
        FROM (
                (SELECT ST_GeomFromText('LINESTRING ZM (1 2 3 NaN,3 4 10 5,5 6 NaN NaN)',4326) As the_geom) ) As foo1 CROSS JOIN ((SELECT CAST(Null As geometry) As the_geom)) As foo2 LIMIT 10;

On my system, the above returns the expected:

ERROR:  Hole 0 is not a line 

Change History (5)

comment:1 by robe, 8 months ago

Summary: berrie 32bit failing on garden testsberrie 32bit failing on garden tests on ST_MakePolygon

comment:2 by strk, 8 weeks ago

Berrie is still failing (PG15): https://debbie.postgis.net/view/PostGIS/job/PostGIS_Worker_Run/label=berrie/5915/console

But the console output doesn't have much information, where is the script to tweak to get that detail ?

comment:3 by Sandro Santilli <strk@…>, 8 weeks ago

In 2df90f2a/git:

Show last lines of garden logs on failure, pre-drop the gardendb

References #5636

comment:4 by strk, 8 weeks ago

I tried getting more output but it still doesn't help, check this out: https://debbie.postgis.net/view/PostGIS/job/PostGIS_Worker_Run/label=berrie/5916/console

19:59:02 -------------------------------------------------
19:59:02 PostGIS garden tests in progress (it will take time)
19:59:02 -------------------------------------------------
19:59:02 psql -X -ad postgis_garden < \
19:59:02 	../doc/postgis_gardentest_35.sql \
19:59:02 	> postgis_garden_result.txt 2>&1 || { \
19:59:02 	tail postgis_garden_result.txt; false; }
20:00:20 INSERT 0 1
20:00:20 			BEGIN;
20:00:20 BEGIN
20:00:20 				 INSERT INTO postgis_garden_log35_output(logid, log_output)
20:00:20 				SELECT logid, query_to_xml(log_sql, false,false,'') As log_output
20:00:20 				    FROM postgis_garden_log35 ORDER BY logid DESC LIMIT 1;UPDATE postgis_garden_log35 SET log_end = clock_timestamp()
20:00:20 server closed the connection unexpectedly
20:00:20 	This probably means the server terminated abnormally
20:00:20 	before or while processing the request.
20:00:20 connection to server was lost

How did you get the ST_MakePolygon call Regina ?

in reply to:  4 comment:5 by robe, 8 weeks ago

Replying to strk:

I tried getting more output but it still doesn't help, check this out: https://debbie.postgis.net/view/PostGIS/job/PostGIS_Worker_Run/label=berrie/5916/console

19:59:02 -------------------------------------------------
19:59:02 PostGIS garden tests in progress (it will take time)
19:59:02 -------------------------------------------------
19:59:02 psql -X -ad postgis_garden < \
19:59:02 	../doc/postgis_gardentest_35.sql \
19:59:02 	> postgis_garden_result.txt 2>&1 || { \
19:59:02 	tail postgis_garden_result.txt; false; }
20:00:20 INSERT 0 1
20:00:20 			BEGIN;
20:00:20 BEGIN
20:00:20 				 INSERT INTO postgis_garden_log35_output(logid, log_output)
20:00:20 				SELECT logid, query_to_xml(log_sql, false,false,'') As log_output
20:00:20 				    FROM postgis_garden_log35 ORDER BY logid DESC LIMIT 1;UPDATE postgis_garden_log35 SET log_end = clock_timestamp()
20:00:20 server closed the connection unexpectedly
20:00:20 	This probably means the server terminated abnormally
20:00:20 	before or while processing the request.
20:00:20 connection to server was lost

How did you get the ST_MakePolygon call Regina ?

You need to show a couple of lines before.

How it works, it inserts the SQL into the postgis_garden_log35 table, and then it runs that line. It's the running that causes the crash, but the insert statement to postgis_garden_log35 just before the insert to postgis_garden_log35_output is what you want to catch.

Note: See TracTickets for help on using tickets.