25.07.2024 19:25, Andrew Dunstan 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 i
On 2024-07-24 We 4:58 PM, Thomas Munro wrote:
On Thu, Jul 25, 2024 at 1:00 AM Alexander Lakhin 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, with
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
On Thu, Jul 25, 2024 at 1:00 AM Alexander Lakhin 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 a
