This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: FAIL: string/tst-strcoll-overflow
On 01/24/2017 01:18 PM, Stefan Liebler wrote:
On 01/23/2017 03:35 PM, Florian Weimer wrote:
On 01/16/2017 09:24 AM, Stefan Liebler wrote:
On 01/13/2017 11:14 PM, 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
Has anyone else seen this?
As information:
This test fails on s390 and a machine from Florian Weimer, too.
See "Re: [PATCH] support: Introduce new subdirectory for test
infrastructure"
https://sourceware.org/ml/libc-alpha/2016-12/msg00391.html and
follow-Ups.
I came up with the attached patch to fix this test.
Do you know if there are archs / machines which run into the timeout
after commit "strcoll: improve performance by removing the cache
(#15884)"
(https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=0742aef6e52a935f9ccd69594831b56d807feef3)?
I'm not sure if there are any such machines. I expect a large run time
(several minutes) on some machines, even relatively current ones, which
is why I think this should remain an xtest.
On s390, the test is passing with your patch as strcoll returns far
before the timeout.
On my intel / power machines, too.
Good. Siddhesh, is it okay to commit this test fix at this point?
Thanks,
Florian