From: Johannes Sixt <j6t@kdbg.org>
Date: Thu, 06 Nov 2025 18:27:57 GMT
Subject: Re: v2.52.0-rc0 test failure on cygwin
Message-ID: <bdba6156-e286-492f-a64d-52bdcf074ea1@kdbg.org>
In-Reply-To: <aQx-RnNX28BPU2cS@pks.im>

Am 06.11.25 um 11:53 schrieb Patrick Steinhardt:
> On Tue, Nov 04, 2025 at 11:49:46PM +0000, Ramsay Jones wrote:
>> So, not really an answer, but I have noted several times over the years
>> that cygwin seems to delay setting some file attributes until after the
>> process has exited ... [yeah, I don't see how either! ;) ].
> 
> What? That's horrible if true. How doesn't this cause more issues?

Unlike POSIX write(), Windows's WriteFile() doesn't update the
modification time stamp immediately. It's only updated when the last
file handle is closed.

https://learn.microsoft.com/en-us/windows/win32/api/fileapi/nf-fileapi-writefile

> When writing to a file, the last write time is not fully updated until
> all handles used for writing have been closed.

-- Hannes