From: | Noah Misch <noah(at)leadboat(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: buildfarm and "rolling release" distros |
Date: | 2014-07-02 02:58:20 |
Message-ID: | 20140702025820.GA1596750@tornado.leadboat.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Jul 01, 2014 at 08:35:16PM -0400, Tom Lane wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> > On Tue, Jul 1, 2014 at 12:49 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> >> I'm also not sure how to designate these machines. The buildfarm server
> >> metadata isn't designed for auto-updating build platforms. But no doubt if
> >> necessary we can come up with something.
>
> > Off-hand, it seems like we could give it a try, and abandon the effort
> > if it proves too problematic.
>
> If a majority of buildfarm critters were like that, it'd be too confusing.
> But as long as they are few, not all following the same update stream,
> and well labeled in the buildfarm status page, I think we could cope.
+1. The buildfarm has one such member already, anchovy, and I recall it
having given at least one helpful forewarning. It shows as "Arch Linux
testing [updated daily]", which is sufficient annotation for me. Its failure
rate has been low; member-caused failures due to ENOSPC and other miscellany
are a good deal more common.
--
Noah Misch
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Abhijit Menon-Sen | 2014-07-02 03:07:09 | Re: pg_xlogdump --stats |
Previous Message | Fujii Masao | 2014-07-02 02:52:04 | Re: Audit of logout |