[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: multiple failures for info tests on cygwin
From: |
Patrice Dumas |
Subject: |
Re: multiple failures for info tests on cygwin |
Date: |
Sat, 21 Sep 2024 12:10:33 +0200 |
On Sat, Sep 21, 2024 at 10:32:07AM +0300, Eli Zaretskii wrote:
> > Date: Fri, 20 Sep 2024 23:43:16 +0200
> > From: Patrice Dumas <pertusus@free.fr>
> > Cc: bug-texinfo@gnu.org
> >
> > On Fri, Sep 20, 2024 at 10:21:01PM +0300, Eli Zaretskii wrote:
> > > > Date: Fri, 20 Sep 2024 20:43:45 +0200
> > > > From: Patrice Dumas <pertusus@free.fr>
> > > >
> > > > Many info tests on cygwin-32 fail (release 7.1 branch). I attach the
> > > > info tests log, I can provide more information on configure output, and
> > > > some other logs if needed.
> > > >
> > > > =====================================================
> > > > GNU Texinfo 7.1.1-20240920: info/test-suite.log
> > > > =====================================================
> > > >
> > > > # TOTAL: 87
> > > > # PASS: 51
> > > > # SKIP: 0
> > > > # XFAIL: 0
> > > > # FAIL: 36
> > > > # XPASS: 0
> > > > # ERROR: 0
> > >
> > > That's most probably the side effect of using Cygwin tools again: the
> > > native port of info cannot run many of the tests because the test rig
> > > uses features not supported by native Windows programs (emulation of
> > > terminals and other such stuff). When running the tests with MSYS,
> > > the test suite detects that and skips those tests, but since you run
> > > them with Cygwin, I'm guessing that the way the test suite detects
> > > Windows ports fails for some reason.
> > >
> > > My records from running the test suite in Texinfo-7.1 indicate that 56
> > > of the info tests were skipped, whereas above you say that none were
> > > skipped. So I'm quite sure this is the reason.
> >
> > Actually, my feeling is that it is the absence of posix_openpt that
> > triggers have_ptys to be false, which in turn causes pseudotty not to
> > be built. In the CI tests, cygwin have posix_openpt, while mingw (in
> > cygwin) does not.
>
> It's that, and the fact that the tests use fifos, which native Windows
> programs cannot support, either. And maybe more.
>
> Whatever PTY Cygwin can produce, the native Windows Info reader is
> extremely unlikely to be able to use.
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.
--
Pat
- multiple failures for info tests on cygwin, Patrice Dumas, 2024/09/20
- Re: multiple failures for info tests on cygwin, Eli Zaretskii, 2024/09/21
- Re: multiple failures for info tests on cygwin,
Patrice Dumas <=
- Re: multiple failures for info tests on cygwin, Gavin Smith, 2024/09/21
- Re: multiple failures for info tests on cygwin, Ken Brown, 2024/09/21
- Re: multiple failures for info tests on cygwin, Patrice Dumas, 2024/09/21