Re: Recent eelpout failures on 9.x branches

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Recent eelpout failures on 9.x branches
Date: 2020-12-01 22:50:21
Message-ID: CA+hUKGJJeK-cM2Hzymh1Su3-aKQQLp0s1ojwjrRDF3f+oB8iYw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Dec 2, 2020 at 11:36 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Perhaps this is just a question of the machine being too slow to complete
> the test, in which case we ought to raise wal_sender_timeout. But it's
> weird that it would've started to fail just now, because I don't really
> see any changes in those branches that would explain a week-old change
> in the test runtime.

Unfortunately, eelpout got kicked off the nice shiny ARM server it was
running on so last week I moved it to a rack mounted Raspberry Pi. It
seems to be totally I/O starved causing some timeouts to be reached,
and I'm looking into fixing that by adding fast storage. This may
take a few days. Sorry for the noise.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2020-12-01 23:05:21 Re: proposal: unescape_text function
Previous Message Tom Lane 2020-12-01 22:39:24 Re: Setof RangeType returns