| From: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Subject: | Re: Sporadic connection-setup-related test failures on Cygwin in v15- |
| Date: | 2024-07-25 03:00:00 |
| Message-ID: | 4c942081-081d-ed30-dd54-13544177840c@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
24.07.2024 23:58, Thomas Munro wrote:
> +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.
Yeah, it looks like lorikeet votes +[1] for your proposal.
(I suppose it failed due to the same signal processing issue, just another
way.)
[1] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=lorikeet&dt=2024-07-24%2008%3A54%3A07
Best regards,
Alexander
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2024-07-25 03:05:44 | Re: Parent/child context relation in pg_get_backend_memory_contexts() |
| Previous Message | Nathan Bossart | 2024-07-25 02:58:52 | Re: optimizing pg_upgrade's once-in-each-database steps |