help-libidn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: libidn2-2.3.0, Solaris 11.3 and one test failure


From: Jeffrey Walton
Subject: Re: libidn2-2.3.0, Solaris 11.3 and one test failure
Date: Thu, 2 Apr 2020 11:11:54 -0400

> What does 88 on Solaris mean ?

$ grep 88 /usr/include/sys/errno.h
...
 * University Copyright- Copyright (c) 1982, 1986, 1988
#define EILSEQ  88      /* Illegal byte sequence.               */

On Thu, Apr 2, 2020 at 11:02 AM Tim Rühsen <address@hidden> wrote:
>
> I remember seeing errors on Solaris. Iconv and charsets did not properly
> work or were not properly implemented on Solaris.
>
> The two cited lines don't mean anything - some failures are on purpose
> and expected. On Debian Linux I get errno 84 for those (Invalid or
> incomplete multibyte or wide character).
>
> What does 88 on Solaris mean ?
>
> Regards, Tim
>
> On 4/2/20 4:08 PM, Jeffrey Walton wrote:
> >
> > It looks like libidn2 is catching one self test failure:
> >
> > PASS: test-punycode
> > FAIL: test-lookup
> > PASS: test-register
> > PASS: test-strerror
> > PASS: test-tounicode
> > ...
> > # TOTAL: 5
> > # PASS:  4
> > # SKIP:  0
> > # XFAIL: 0
> > # FAIL:  1
> > # XPASS: 0
> > # ERROR: 0
> >
> > I see the failures but nothing jumps out at me. It all looks Greek
> > (Chinese) to me:
> >
> > u8_to_u32(≮𝟎.謖SS�) failed (88)
> > u8_to_u32(≮𝟎.謖ss�) failed (88)
> >
> > Attached is test-suite.log.
> >



reply via email to

[Prev in Thread] Current Thread [Next in Thread]