Thread
Commits
-
Mark unsafe_tests module as not runnable with installcheck
- 13196cc75598 12.15 landed
- baf7f450dbec 13.11 landed
- 4642c2b56a99 14.8 landed
- 9e236f943676 15.3 landed
- 872e3d150e9a 16.0 landed
-
unsafe_tests module
Andrew Dunstan <andrew@dunslane.net> — 2023-02-22T11:47:34Z
Given its nature and purpose as a module we don't want to run against an installed instance, shouldn't src/test/modules/unsafe_tests have NO_INSTALLCHECK=1 in its Makefile and runningcheck:false in its meson.build? cheers andrew -- Andrew Dunstan EDB:https://www.enterprisedb.com
-
Re: unsafe_tests module
Andres Freund <andres@anarazel.de> — 2023-03-12T00:12:21Z
Hi, On 2023-02-22 06:47:34 -0500, Andrew Dunstan wrote: > Given its nature and purpose as a module we don't want to run against an > installed instance, shouldn't src/test/modules/unsafe_tests have > NO_INSTALLCHECK=1 in its Makefile and runningcheck:false in its meson.build? Seems like a good idea to me. Greetings, Andres Freund
-
Re: unsafe_tests module
Andrew Dunstan <andrew@dunslane.net> — 2023-03-12T13:06:46Z
On 2023-03-11 Sa 19:12, Andres Freund wrote: > Hi, > > On 2023-02-22 06:47:34 -0500, Andrew Dunstan wrote: >> Given its nature and purpose as a module we don't want to run against an >> installed instance, shouldn't src/test/modules/unsafe_tests have >> NO_INSTALLCHECK=1 in its Makefile and runningcheck:false in its meson.build? > Seems like a good idea to me. > Thanks, done. cheers andrew -- Andrew Dunstan EDB:https://www.enterprisedb.com