MIME-Version: 1.0
References: <54954.1559649728@sss.pgh.pa.us>
In-Reply-To: <54954.1559649728@sss.pgh.pa.us>
From: Julien Rouhaud <rjuju123@gmail.com>
Date: Wed, 5 Jun 2019 20:57:13 +0200
Message-ID: 
 <CAOBaU_bBRJ04U5UAyUh+BnxZxuH7hs=xzhc-KTG9YqUPQje=gA@mail.gmail.com>
Subject: Re: Please update buildfarm members to current script version
 (REL_10)
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: buildfarm-members@lists.postgresql.org
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Tue, Jun 4, 2019 at 2:02 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Could I bug people to update their animals to the latest release
> of the buildfarm client script?  Since this commit:
>
> https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=40b132c1a
>
> animals running pre-REL_10 scripts will not report full information
> about failures in the pg_upgrade test.  This is particularly problematic
> right now, because we're wondering what the heck is going on with
> intermittent failures in that test:
>
> https://www.postgresql.org/message-id/28041.1558408547@sss.pgh.pa.us
>
> There's a patch in place to try to gather more info about that, but
> it's useless if the affected animal doesn't capture the regression.diffs
> file.  Thus for example, mayfly's latest failure might have yielded
> useful information, except it's using REL_8 :-(.  We're only seeing maybe
> one occurrence every couple of weeks, so missed opportunities are painful.
>
> Please update at your earliest convenience.

FTR I updated lapwing.  I noticed that the non-master branches weren't
being tested for an embarrassing amount for time, so I fixed that at
the same time.