| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Alexander Lakhin <exclusion(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Sporadic connection-setup-related test failures on Cygwin in v15- |
| Date: | 2024-07-25 16:25:49 |
| Message-ID: | 01267d78-24db-472b-af93-c21b87acf0b7@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2024-07-24 We 4:58 PM, Thomas Munro wrote:
> On Thu, Jul 25, 2024 at 1:00 AM Alexander Lakhin<exclusion(at)gmail(dot)com> wrote:
>> The important fact here is that this failure is not reproduced after
>> 7389aad63 (in v16), so it seems that it's somehow related to signal
>> processing. Given that, I'm inclined to stop here, without digging deeper,
>> at least until there are plans to backport that fix or something...
> +1. I'm not planning to back-patch that work. Perhaps lorikeet
> could stop testing releases < 16? They don't work and it's not our
> bug[1]. We decided not to drop Cygwin support[2], but I don't think
> we're learning anything from investigating that noise in the
> known-broken branches.
Sure, it can. I've made that change.
cheers
andrew
--
Andrew Dunstan
EDB:https://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2024-07-25 16:32:24 | Re: proposal: schema variables |
| Previous Message | Laurenz Albe | 2024-07-25 16:03:23 | Re: Reducing the log spam |