On Sat, Sep 21, 2024 at 05:54:15PM -0400, Ken Brown wrote: > On 9/21/2024 8:07 AM, Gavin Smith wrote: > > On Sat, Sep 21, 2024 at 12:10:33PM +0200, Patrice Dumas wrote: > > > This platform does not test the native Windows Info reader, it is the > > > cygwin info reader. So these tests fail in a 'pure' Cygwin setup, there > > > is no mingw here, the comparison with mingw was in order to explain why > > > the tests are skipped with mingw (on MSYS or on Cygwin) and not on > > > 'pure' Cygwin. > > > > It's hard for me to know what the problem is without building on Cygwin > > myself, which I am not able or willing to do at the current time. The > > log files you sent appear to show that the pseudotty program is built > > and used in the tests, but all the tests time out. > I'm Cygwin's Texinfo maintainer, and I have two comments about this thread. > > 1. According to the OP, these failures occurred on 32-bit Cygwin. This > platform has been unsupported by the Cygwin project for about 3 years. In > particular, Cygwin will never provide recent Texinfo packages for the 32-bit > case, so I don't think the Texinfo maintainers should waste time worrying > about this.
Ok, thanks for the information. > 2. Cygwin provides its own build service (based on GitHub actions) for use > by package maintainers. When I've used this with recent versions of > Texinfo, I have found that many tests fail; but they all pass when I run > them locally. I've never been able to figure out what's different about the > GitHub actions setup that causes these failures, but I haven't worried about > it since all tests pass on my system. Good to hear. I'll probably try to skip the info tests on Cygwin 64 and see if the texi2any testsuites pass. -- Pat
