Re: Robocopy might be not robust enough for never-ending testing on Windows - Mailing list pgsql-hackers

From Alexander Lakhin
Subject Re: Robocopy might be not robust enough for never-ending testing on Windows
Date
Msg-id f3bfed40-68e9-e839-c555-a3ffa50e0195@gmail.com
Whole thread Raw
In response to Re: Robocopy might be not robust enough for never-ending testing on Windows  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Hello Andrew,

14.09.2024 17:22, Andrew Dunstan wrote:
>
> On 2024-09-14 Sa 9:00 AM, Alexander Lakhin wrote:
>> While trying to reproduce inexplicable drongo failures (e. g., [1])
>> seemingly related to BackgroundPsql, I stumbled upon close, but not
>> the same issue. ...
>>
>
> Interesting, good detective work. Still, wouldn't this mean drongo would fail consistently?

Yes, I think drongo is suffering from another disease, we're yet to find
which.

>
> I wonder why we're using robocopy instead of our own RecursiveCopy module?
>

AFAICS, robocopy is also used by regress.exe, so switching to the perl
module would require perl even for regress tests. I know that perl was
a requirement for MSVC builds, but maybe that's not so with meson...

Best regards,
Alexander



pgsql-hackers by date:

Previous
From: Junwang Zhao
Date:
Subject: Re: why there is not VACUUM FULL CONCURRENTLY?
Next
From: Tom Lane
Date:
Subject: Re: Obsolete comment in pg_stat_statements