Re: [bug-libunistring] [platform-testers] libunistring 0.9.6 first release candidate

[Dagobert Michelsen]

Hi Daiki,

Am 29.06.2015 um 03:13 schrieb Daiki Ueno <address@hidden>:
> Dagobert Michelsen <address@hidden> writes:
> 
>> I have two remaining failing tests on Solaris 10 Sparc only:
>> 
>>> FAIL: test-u16-strstr
>>> =====================
>>> 
>>> FAIL test-u16-strstr (exit status: 142)
>>> 
>>> FAIL: test-u32-strstr
>>> =====================
>>> 
>>> FAIL test-u32-strstr (exit status: 142)
> 
> Sorry, I have no idea what is happening there.  Are you able to run them
> individually?  I wonder why there is no indication of error locations,
> while the ASSERT macro is supposed to do that.

I found these in the logs:

> ../build-aux/test-driver: line 107: 24480 Alarm Clock             "$@" > 
> $log_file 2>&1
> FAIL: test-u16-strstr

> ../build-aux/test-driver: line 107: 25343 Alarm Clock             "$@" > 
> $log_file 2>&1
> FAIL: test-u32-strstr

Maybe this gives you a hint?


Best regards

  — Dago

-- 
"You don't become great by trying to be great, you become great by wanting to 
do something,
and then doing it so hard that you become great in the process." - xkcd #896

smime.p7s
Description: S/MIME cryptographic signature