| From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | buildfarm-members(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Please update buildfarm members to current script version (REL_10) |
| Date: | 2019-06-05 18:57:13 |
| Message-ID: | CAOBaU_bBRJ04U5UAyUh+BnxZxuH7hs=xzhc-KTG9YqUPQje=gA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | buildfarm-members |
On Tue, Jun 4, 2019 at 2:02 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sandeep Thakkar | 2019-06-06 06:33:17 | Re: Please update buildfarm members to current script version (REL_10) |
| Previous Message | Bernd Helmle | 2019-06-05 17:40:34 | Re: Please update buildfarm members to current script version (REL_10) |