Re: cygwin v2.55.0 test failures
- From
Ramsay Jones <ramsay@ramsayjones.plus.com>
- Date
- Jul 13, 2026, 20:28 UTC
- Message-ID
- <910f130f-ea0b-4086-a43f-3842b0df0fce@ramsayjones.plus.com>
- In-Reply-To
- <alTGqS2_RmfGHvfV@pks.im>
On 13/07/2026 12:06 pm, Patrick Steinhardt wrote:
> On Fri, Jul 10, 2026 at 07:32:23PM +0100, Ramsay Jones wrote: > [snip]
[snip]
Show 5 quoted lines
> > By the way: I was pondering multiple times over whether or not we should > add Cygwin to our CI matrix. It seems to be sufficiently different from > both MSYS2 and native Win32 to have its own set of compatibility issues, > so that could be worth it?
Hmm, I don't know. It is a distinct platform with its own set of peculiar issues. So, it may be worth it. However, I wouldn't want to expend CI resources on a platform which has an unknown user-base. How many cygwin users are there? (it can sometimes feel like there are very many, sometimes maybe just a handful!). ;)
> For the record: I don't really have much of an opinion on this given > that I tend to not use Windows, except when I (once again) break some > tests there. Especially the path handling si something that tends to > cause lots of confusion on my side.
You are not alone!
ATB, Ramsay Jones