If you run make installcheck in contrib it stops on the first module
that fails. This is mildly annoying from the point of view of the
buildfarm script, which wants to run all the available regression tests.
To solve that I implemented a new target that does run them all and only
fails at the
Andrew Dunstan [EMAIL PROTECTED] writes:
If you run make installcheck in contrib it stops on the first module
that fails. This is mildly annoying from the point of view of the
buildfarm script, which wants to run all the available regression tests.
Yeah. ISTM that make -k installcheck
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
If you run make installcheck in contrib it stops on the first module
that fails. This is mildly annoying from the point of view of the
buildfarm script, which wants to run all the available regression tests.
Yeah. ISTM that make
Andrew Dunstan [EMAIL PROTECTED] writes:
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
If you run make installcheck in contrib it stops on the first module
that fails. This is mildly annoying from the point of view of the
buildfarm script, which wants to run all the available
Tom Lane wrote:
I found the following closely-related suggestion in the Make manual.
It's not quite there because it doesn't seem to provide a way to pass
down the current action (all/clean/install/etc) to the sub-Make.
Any ideas how we could do that?
I've seen the following idea somewhere:
Peter Eisentraut [EMAIL PROTECTED] writes:
I've seen the following idea somewhere:
Looks like you used a variant of this in src/backend/Makefile.
Then again, the original proposal doesn't sound so bad either.
Well, I'd like a more generic fix that we could apply everywhere,
because right now
Peter Eisentraut wrote:
Tom Lane wrote:
I found the following closely-related suggestion in the Make manual.
It's not quite there because it doesn't seem to provide a way to pass
down the current action (all/clean/install/etc) to the sub-Make.
Any ideas how we could do that?
I've seen the
