Re: Should we use make -k on the buildfarm?

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Should we use make -k on the buildfarm?
Date: 2010-11-08 19:49:25
Message-ID: 1289245765.502.8.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On lör, 2010-11-06 at 14:45 -0400, Andrew Dunstan wrote:
> Here's the list of tests from a recent run, leaving out stopping and
> starting the installed postmaster, and locale specifiers:
>
> SCM-checkout
> configure
> make
> check
> make-contrib
> make-install
> install-contrib
> initdb
> install-check
> pl-install-check
> contrib-install-check
> ecpg-check
>
> Currently, the implied dependency list is in this order. We could have
> "make-contrib" depend only on "make" rather than "check",
> "pl-install-check" and "contrib-install-check" depend on "initdb",
> and "ecpg-check" depend on "make" rather than anything that comes
> after. I think that's about the limit of what we could sensibly relax

In principle you could get this down to

SCM-checkout
configure
make -k world
make -k check-world # target doesn't exist yet
make -k install-world
initdb
make -k installcheck-world

That way you don't have to update the buildfarm code every time a new
test suite is added.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2010-11-08 19:56:31 Re: UNION ALL has higher cost than inheritance
Previous Message Merlin Moncure 2010-11-08 19:46:20 Re: proposal: plpgsql - iteration over fields of rec or row variable