| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alexander Lakhin <exclusion(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
| Subject: | Re: Recent 027_streaming_regress.pl hangs |
| Date: | 2024-07-31 16:58:37 |
| Message-ID: | 4205a24d-a1ce-4658-99d7-b00d8472d4c0@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2024-07-31 We 12:05 PM, Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2024-07-31 17:39:45 | Re: can we mark upper/lower/textlike functions leakproof? |
| Previous Message | Alexander Korotkov | 2024-07-31 16:40:48 | Re: [HACKERS] make async slave to wait for lsn to be replayed |