Horton

Re: Recent 027_streaming_regress.pl hangs

Andrew Dunstan <andrew@dunslane.net>

View thread View on postgr.es
From: Andrew Dunstan <andrew@dunslane.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alexander Lakhin <exclusion@gmail.com>, Thomas Munro <thomas.munro@gmail.com>, Michael Paquier <michael@paquier.xyz>, pgsql-hackers <pgsql-hackers@postgresql.org>, Andres Freund <andres@anarazel.de>, Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Date: 2024-07-31T16:58:37Z
Lists: pgsql-hackers 
On 2024-07-31 We 12:05 PM, Tom Lane wrote:
> Andrew Dunstan <andrew@dunslane.net> writes:
>> There seem to be a bunch of recent failures, and not just on crake, and
>> not just on HEAD:
>> <https://buildfarm.postgresql.org/cgi-bin/show_failures.pl?max_days=14&member=&stage=recoveryCheck&filter=Submit>
> There were a batch of recovery-stage failures ending about 9 days ago
> caused by instability of the new 043_vacuum_horizon_floor.pl test.
> Once you take those out it doesn't look quite so bad.



We'll see. I have switched crake from --run-parallel mode to --run-all 
mode i.e. the runs are serialized. Maybe that will be enough to stop the 
errors. I'm still annoyed that this test is susceptible to load, if that 
is indeed what is the issue.


cheers


andrew


--

Andrew Dunstan
EDB: https://www.enterprisedb.com

Commits

  1. Log more info when wait-for-catchup tests time out.

  2. Add a new slot sync worker to synchronize logical slots.