This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Aarch64 test results and questions


On 29/07/2019 17:18, Florian Weimer wrote:
> * Carlos O'Donell:
>> On 7/29/19 11:20 AM, Szabolcs Nagy wrote:
>>> On 29/07/2019 14:42, Carlos O'Donell wrote:
>>>> On 7/29/19 4:18 AM, Szabolcs Nagy wrote:
>>>
>>> the aarch64 buildbot is red because
>>>
>>> FAIL: resolv/tst-resolv-search
>>> FAIL: resolv/tst-resolv-trailing
>>>
>>> both are timeouts (i haven't seen them before):
>>>
>>> $ cat resolv/tst-resolv-search.out
>>> Timed out: killed the child process
>>> Termination time: 2019-07-29T15:09:55.891714
>>> Last write to standard output: 2019-07-29T15:09:35.886436
>>> $ cat resolv/tst-resolv-trailing.out
>>> Timed out: killed the child process
>>> Termination time: 2019-07-29T15:10:16.632413
>>> Last write to standard output: 2019-07-29T15:09:56.626538
>>>
>>> i'm not sure if these just intermittent failures or real,
>>> but at least the nss/tst-nss-files-hosts-long failure is
>>> gone now.
>>
>> Florian,
>>
>> Any idea?
> 
> Some test failures may be due to iptables/nftables issues.  In the past,
> support_enter_network_namespace in support/resolv_test.c worked around
> that because there was no connection tracking in the new namespace.
> 
> Does the kernel log anything about connection tracking table overflow?
> 
> These tests do not print anything on success.  You can run them with
> --verbose to get some logging.

i could not reproduce the failures, i did not see anything weird
in kernel logs.

the aarch64 buildbot is now green.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]