From: Rachel Sibley <rasibley@redhat.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: chrubis@suse.cz, catalin.marinas@arm.com,
"Memory Management" <mm-qe@redhat.com>,
"CKI Project" <cki-project@redhat.com>,
"Iñaki Malerba" <imalerba@redhat.com>,
"Will Deacon" <will@kernel.org>,
"Jan Stancek" <jstancek@redhat.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: ❌ FAIL: Test report for kernel 5.9.0-rc8 (arm-next)
Date: Wed, 7 Oct 2020 13:11:03 -0400 [thread overview]
Message-ID: <fa54b3f8-804a-5e93-d3a3-ff075dba42dd@redhat.com> (raw)
In-Reply-To: <20201007053345.4xbyjx4u4ccwkep5@vireshk-i7>
On 10/7/20 1:33 AM, Viresh Kumar wrote:
> On 06-10-20, 10:09, Rachel Sibley wrote:
>>
>>
>> On 10/6/20 8:45 AM, Will Deacon wrote:
>>> [+Viresh as he wrote this test]
>>>
>>> On Tue, Oct 06, 2020 at 12:54:59PM +0200, Iñaki Malerba wrote:
>>>> El 6/10/20 a las 10:22, Will Deacon escribió:
>>>>> On Tue, Oct 06, 2020 at 01:15:18AM -0000, CKI Project wrote:
>>>>>> We ran automated tests on a recent commit from this kernel tree:
>>>>>>
>>>>>> Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
>>>>>> Commit: e37569e28eea - Merge branch 'for-next/late-arrivals' into for-kernelci
>>>>>>
>>>>>> The results of these automated tests are provided below.
>>>>>>
>>>>>> Overall result: FAILED (see details below)
>>>>>> Merge: OK
>>>>>> Compile: OK
>>>>>> Tests: FAILED
>>>>>>
>>>>>> All kernel binaries, config files, and logs are available for download here:
>>>>>>
>>>>>> https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix=datawarehouse/2020/10/05/614774
>>>>>
>>>>> Hmm, this link doesn't seem to work (the '10' directory doesn't exist). Do I
>>>>> just need to wait a bit longer?
>>>>
>>>> Thanks for reporting this!
>>>>
>>>> There was a problem on the script that uploads the files. It's fixed now
>>>> and the files are deploying. In a few minutes everything should be there.
>>>>
>>>> Your report also made us realize the link is incorrect, as the prefix
>>>> should be `datawarehouse-public` instead of `datawarehouse` (with the
>>>> correct prefix it should link to the correct folder).
>>>>
>>>> The (now working) link is the following:
>>>>
>>>> https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix=datawarehouse-public/2020/10/05/614774
>>>>
>>>> Sorry for the troubles,
>>>
>>> Thanks, that works now. It looks like the failure is in the timed semaphore
>>> tests:
>>>
>>> semop03.c:55: TFAIL: unexpected failure: EAGAIN/EWOULDBLOCK (11)
>>>
>>> where the text expects EINTR, but assumedly the timeout is kicking in
>>> so we get EAGAIN. I don't see how the arm64 tree can be causing that, and I
>>> rather suspect that the test is just racy (the timeout is pretty small --
>>> 10ms iiuc).
>
> That is one possible explanation for sure.
>
> Rachel, can you please increase the timeout to something sufficiently
> big enough and try again ? Something like this:
>
> - tst_ts_set_sec(&timeout, 0);
> + tst_ts_set_sec(&timeout, 2);
>
> I saw similar issues with very small timeouts and 10ms kind of worked
> all the time. I think we need to increase it further.
Thanks for your patch Viresh, just ran it on the same machine/kernel for 100 loops, and happy to confirm I no longer
see the failures, increasing the timeout worked well.
Thanks!
Rachel
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-10-07 17:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 1:15 ❌ FAIL: Test report for kernel 5.9.0-rc8 (arm-next) CKI Project
2020-10-06 8:22 ` Will Deacon
[not found] ` <ce1d05d0-50b3-ac86-f1d6-c82f59317582@redhat.com>
2020-10-06 12:45 ` Will Deacon
[not found] ` <2c19157a-a31f-dfe5-de05-94d73cc1be67@redhat.com>
2020-10-07 5:33 ` Viresh Kumar
2020-10-07 17:11 ` Rachel Sibley [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fa54b3f8-804a-5e93-d3a3-ff075dba42dd@redhat.com \
--to=rasibley@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=chrubis@suse.cz \
--cc=cki-project@redhat.com \
--cc=imalerba@redhat.com \
--cc=jstancek@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mm-qe@redhat.com \
--cc=viresh.kumar@linaro.org \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).