| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Buildfarm coverage (was Re: OK, ready for RC1 or Beta6) |
| Date: | 2004-12-03 22:02:05 |
| Message-ID: | 13568.1102111325@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> The configuration is chosen in the config file for each member, rather
> than being dictated centrally.
This is good. Now what we need is a little cooperation among the
buildfarm team to make sure that the collective set of cases tested
covers all the interesting combinations of configure flags, as per
my followup ...
> A single member can run more than one branch, and per-branch config can
> be set up. A single machine can run more than one farm member (e.g. to
> use different compilers).
Yeah, on platforms where there's a non-gcc vendor compiler, testing with
the vendor compiler is very interesting.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-12-03 22:05:49 | Re: OK, ready for RC1 or Beta6 |
| Previous Message | Andrew Dunstan | 2004-12-03 21:49:46 | Re: OK, ready for RC1 or Beta6 |