This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: FAIL: string/tst-strcoll-overflow
On Saturday 14 January 2017 03:44 AM, H.J. Lu wrote:
> On x86-64 with 32GB RAM under kernel 4.9.3, I got
>
> string/tst-strcoll-overflow
> 0
> Expected signal 'Alarm clock' from child, got none
IIRC the test never actually completes, so the expected return there is
a SIGALRM. In your case the test managed to complete (you've got some
monster hardware there!) which is why the test 'failed'.
Perhaps it would be a good idea to modify the skeleton to always
consider exit code 0 as success and then have the expected signals or
return codes be additional success factors.
Siddhesh