Re: test results on Cygwin 1.7.30

Eric Blake wrote: > > Test results of a Gnulib POSIX testdir on Cygwin 1.7.30 (32-bit): > > Can we repeat with modern cygwin 2.8.2? You can do so using the usual steps: 1. On a development machine: - Check out gnulib. $ ./gnulib-tool --create-testdir --dir=/tmp/testdir-posix --with-te

Re: test results on Cygwin 1.7.30

On 08/16/2017 07:06 PM, Bruno Haible wrote: > Test results of a Gnulib POSIX testdir on Cygwin 1.7.30 (32-bit): Can we repeat with modern cygwin 2.8.2? -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3266 Virtualization: qemu.org | libvirt.org signature.asc Desc

test results on Cygwin 1.7.30

Test results of a Gnulib POSIX testdir on Cygwin 1.7.30 (32-bit): FAIL: test-fclose = ../../gltests/test-fclose.c:74: assertion 'lseek (fd, 0, SEEK_CUR) == 3' failed FAIL test-fclose.exe (exit status: 134) FAIL: test-fmal2 ../../gltests/test-fma2.h:558: asserti

Re: test results on Cygwin

Simon Josefsson writes: > I'm running another build now. We are down to two failed self-tests under cygwin, see: http://autobuild.josefsson.org/gnulib/log-201005030918958478000.txt The failures are: file_has_acl("tmpdir0") returned yes, expected no FAIL: test-file-has-acl.sh Unconnected sock

Re: test results on Cygwin

Bruno Haible writes: > Simon Josefsson wrote: >> > Thanks, it should likely solve the problem too -- I'm running a Windows >> > cygwin build to test it now. >> >> Yep: >> >> http://autobuild.josefsson.org/gnulib/log-20100425225612508.txt >> ... >> There is a bunch of printf-failures in ther

Re: test results on Cygwin

Simon Josefsson wrote: > > Thanks, it should likely solve the problem too -- I'm running a Windows > > cygwin build to test it now. > > Yep: > > http://autobuild.josefsson.org/gnulib/log-20100425225612508.txt > ... > There is a bunch of printf-failures in there that I don't recall, but > othe

Re: test results on Cygwin

Hi, On 2010-04-05 I reported: > A simplified test case is attached. It crashes when optimized with -O2 > and works fine without optimization: > ... > The same behaviour also occurs when the test case uses the gnulib replacement > of mbsrtowcs. Therefore I think it's not a bug in Cygwin's mbsrtowcs

Re: test results on Cygwin

> Failures on Cygwin 1.7.2 > > > test-mbsnrtowcs.c:181: assertion failed > ./test-mbsnrtowcs2.sh: line 15:  5708 Aborted                 (core dumped) > LC_ALL=$LOCALE_FR_UTF8 ./test-mbsnrtowcs${EXEEXT} 2 > FAIL: test-mbsnrtowcs2.sh > > test-mbsrtowcs.c:181: assertion fa

Re: test results on Cygwin

> Failures on Cygwin 1.7.2 > > > test-btowc.c:48: assertion failed > ./test-btowc1.sh: line 15: 2892 Aborted (core dumped) > LC_ALL=$LOCALE_FR ./test-btowc${EXEEXT} 1 > FAIL: test-btowc1.sh > > test-btowc.c:56: assertion failed > ./test-btowc2.sh: line 1

Re: test results on Cygwin

> Failures on Cygwin 1.7.2 > > > Starting test_cond .../bin/sh: line 5: 4200 Aborted > FAIL: test-cond.exe > > Starting test_lock .../bin/sh: line 5: 2296 Aborted > FAIL: test-lock.exe > > Starting test_tls .../bin/sh: line 5: 2656 Aborted > FAIL: test-tls.exe These

test results on Cygwin

Here are the test results of a complete gnulib testdir on Cygwin. Failures on both Cygwin 1.5.25 and 1.7.2 file_has_acl("tmpdir0") returned yes, expected no FAIL: test-file-has-acl.sh Unconnected socket test... passed Connected sockets test... passed Gene