Opened 10 years ago
Closed 10 years ago
#3105 closed defect (fixed)
sfcgal legacy test via extension: ERROR: attempt to redefine parameter "postgis.backend
Reported by: | strk | Owned by: | colivier |
---|---|---|---|
Priority: | medium | Milestone: | PostGIS 2.2.0 |
Component: | sfcgal | Version: | master |
Keywords: | Cc: |
Description
cd regress ./run_test.pl -v --sfcgal --extension sfcgal/legacy.sql ... sfcgal/legacy .. failed (diff expected obtained: /tmp/pgis_reg/test_1_diff) ----------------------------------------------------------------------------- --- sfcgal/legacy_expected 2015-03-28 11:16:04.798484842 +0100 +++ /tmp/pgis_reg/test_1_out 2015-05-04 11:57:26.474192034 +0200 @@ -1,21 +1,73 @@ +psql:00-regress-install/share/contrib/postgis/legacy.sql:654: ERROR: attempt to redefine parameter "postgis.backend" +psql:00-regress-install/share/contrib/postgis/legacy.sql:678: ERROR: attempt to redefine parameter "postgis.backend" ...
Change History (4)
comment:1 by , 10 years ago
comment:2 by , 10 years ago
Does not happen with offline (script-based, rather than extension-based) tests.
comment:3 by , 10 years ago
Got it, the "legacy.sql" script loads the "legacy.sql" enabled script from offline, which in turn loads the shared object from offline. There's then a clash of libraries between the online one and the offline one.
How should "legacy" be tested online ? @robe: how do you want people to enable "legacy" when using an extension ?
comment:4 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Figured by myself, it was already handled in sfcgal-less run (we have support for loading scripts from install dir in run_test.pl!!).
See r13477 for the fix.
Note:
See TracTickets
for help on using tickets.
Precedent discussion about the error is in #2382