Re: test results on Cygwin

[Simon Josefsson]

Bruno Haible <address@hidden> 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-201004252256125080000.txt
>> ...
>> There is a bunch of printf-failures in there that I don't recall, but
>> otherwise it pretty much looks like normal for cygwin.
>
> The failed tests here were:
>
>   FAIL: test-file-has-acl.sh
>
> Known: Weird semantics of Cygwin w.r.t. ACLs and file modes.

Maybe adding some URL references to the script would be useful, to make
sure we are aware of the problem?

>   FAIL: test-mbsnrtowcs2.sh
>   FAIL: test-mbsrtowcs2.sh
>
> These were due to a wctob() bug for which I've added a workaround today.

I'm running another build now.

>   FAIL: test-poll.exe
>
> Known. But will someone handle it?

Maybe we could use the savannah bug tracker to more permanently record
known issues?

>   FAIL: test-u16-casecoll.exe
>   FAIL: test-u32-casecoll.exe
>   FAIL: test-u8-casecoll.exe
>   FAIL: unicase/test-ulc-casecmp1.sh
>   FAIL: unicase/test-ulc-casecoll1.sh
>   FAIL: test-u16-normcoll.exe
>   FAIL: test-u32-normcoll.exe
>   FAIL: test-u8-normcoll.exe
>
> These are typical consequences of a lack of iconv() facility.
> You should install libiconv (prepackaged as part of Cygwin, or
> self-built, does not matter).
>
>   FAIL: test-u16-vasnprintf1.exe
>   FAIL: unistdio/test-u16-vasnprintf2.sh
>   FAIL: unistdio/test-u16-vasnprintf3.sh
>   FAIL: test-u16-vasprintf1.exe
>   FAIL: test-u16-vsnprintf1.exe
>   FAIL: test-u16-vsprintf1.exe
>   FAIL: test-u32-vasnprintf1.exe
>   FAIL: unistdio/test-u32-vasnprintf2.sh
>   FAIL: unistdio/test-u32-vasnprintf3.sh
>   FAIL: test-u32-vasprintf1.exe
>   FAIL: test-u32-vsnprintf1.exe
>   FAIL: test-u32-vsprintf1.exe
>   FAIL: test-u8-vasnprintf1.exe
>   FAIL: unistdio/test-u8-vasnprintf2.sh
>   FAIL: unistdio/test-u8-vasnprintf3.sh
>   FAIL: test-u8-vasprintf1.exe
>   FAIL: test-u8-vsnprintf1.exe
>   FAIL: test-u8-vsprintf1.exe
>   FAIL: test-ulc-vasnprintf1.exe
>   FAIL: unistdio/test-ulc-vasnprintf2.sh
>   FAIL: unistdio/test-ulc-vasnprintf3.sh
>   FAIL: test-ulc-vasprintf1.exe
>   FAIL: test-ulc-vsnprintf1.exe
>   FAIL: test-ulc-vsprintf1.exe
>
> These are also likely a consequence of a lacking iconv(): I did not
> encounter these errors today when testing libunistring-0.9.3 on Cygwin.

I've installed it now, and is rerunning a build.  But shouldn't there be
some better diagnosis than a failed test for a missing library?

/Simon