Opened 5 weeks ago
Last modified 5 weeks ago
#5820 new defect
woodie failing on pg 15 check
Reported by: | robe | Owned by: | robe |
---|---|---|---|
Priority: | blocker | Milestone: | PostGIS 3.6.0 |
Component: | QA/buildbots | Version: | master |
Keywords: | Cc: |
Description
Just noticed woodie is failing on master branch
https://woodie.osgeo.org/repos/30/pipeline/2718/10
psql:/tmp/pgis_reg/loader.out:6: NOTICE: Adding maximum extent constraint psql:/tmp/pgis_reg/loader.out:6: ERROR: could not load library "/woodpecker/src/git.osgeo.org/gitea/postgis/postgis/build/pg15/regress/00-regress-install/lib/postgis-3.6.so": /woodpecker/src/git.osgeo.org/gitea/postgis/postgis/build/pg15/regress/00-regress-install/lib/postgis-3.6.so: cannot open shared object file: Permission denied CONTEXT: SQL statement "SELECT st_ashexewkb( st_setsrid( st_extent( st_envelope(rast)), 0)) FROM public.loadedrast" PL/pgSQL function _add_raster_constraint_extent(name,name,name) line 33 at EXECUTE PL/pgSQL function addrasterconstraints(name,name,name,text[]) line 104 at assignment PL/pgSQL function addrasterconstraints(name,name,name,boolean,boolean,boolean,boolean,boolean,boolean,boolean,boolean,boolean,boolean,boolean,boolean) line 53 at RETURN
not sure what would cause a permissioning issue
Change History (2)
follow-up: 2 comment:1 by , 5 weeks ago
comment:2 by , 5 weeks ago
Replying to strk:
I've seen this happening to me sometime. Sounds like PostgreSQL server not having permissions to read under user dir. Is it happening consistently ? Maybe a race between multiple runs ?
Doesn't look like it's happening all the time. The last commit to master is green.
Should we not concern ourselves with this then?
Note:
See TracTickets
for help on using tickets.
I've seen this happening to me sometime. Sounds like PostgreSQL server not having permissions to read under user dir. Is it happening consistently ? Maybe a race between multiple runs ?