From: Rachel Sibley <rasibley@redhat.com>
To: Will Deacon <will@kernel.org>, Jan Stancek <jstancek@redhat.com>,
Li Wang <liwang@redhat.com>
Cc: catalin.marinas@arm.com, Memory Management <mm-qe@redhat.com>,
skt-results-master@redhat.com,
CKI Project <cki-project@redhat.com>,
Xiaowu Wu <xiawu@redhat.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: ❌ FAIL: Test report for kernel 5.11.0-rc4 (arm-next)
Date: Fri, 22 Jan 2021 14:38:49 -0500 [thread overview]
Message-ID: <f9d423db-eb19-79b1-1ce1-32e6a8adbe0e@redhat.com> (raw)
In-Reply-To: <9eb4b599-3683-5dd5-f336-64b815507cd0@redhat.com>
On 1/22/21 9:57 AM, Rachel Sibley wrote:
>
>
> On 1/22/21 6:49 AM, Will Deacon wrote:
>> On Fri, Jan 22, 2021 at 04:46:27AM -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: 3c50969f0be2 - Merge branches 'for-next/from-tip/irq/urgent', 'for-next/misc', 'for-next/perf', 'for-next/random',
>>> 'for-next/rng', 'for-next/selftests', 'for-next/stacktrace', 'for-next/topology' and 'for-next/vdso' into for-next/core
>>>
>>> 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-public/2021/01/21/621932
>>>
>>> One or more kernel tests failed:
>>>
>>> aarch64:
>>> ❌ LTP
>>
>> Hmm, this seems to be as a result of this error:
>>
>> 7 netns_breakns 1 TINFO: timeout per run is 0h 5m 0s
>> 8 RTNETLINK answers: Operation not permitted
>> 9 netns_breakns 1 TBROK: unable to create veth pair devices
>> 10 Cannot find device "veth0"
>>
>> (https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/datawarehouse-public/2021/01/21/621932/build_aarch64_redhat%3A1078955/tests/LTP/9444882_aarch64_1_containers.fail.log)
>>
>>
>> which doesn't look immediately related to anything we've queued on the arm64
>> side. CKI folks -- have you seen this failure anywhere else, and is it
>> reproducible?
>>
>
> The netns suite was recently rewritten upstream so most likely a result of an unstable test case, Li/Jan do you have more details ?
> I'm attempting to reproduce it right now, will keep you you updated:
I was unable to reproduce this, so maybe a transient error ? I added this failure to have our bot triager monitor it,
if it tags additional pipelines we can follow up and report and/or mask it going forward. Please feel free to ignore
for now, thank you!
>
> https://github.com/linux-test-project/ltp/commit/cc82df62b26f6bbf63a4f375a98019af44ae023d
>
> Thanks,
> Rachel
>
>> Thanks,
>>
>> Will
>>
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-01-22 19:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 4:46 ❌ FAIL: Test report for kernel 5.11.0-rc4 (arm-next) CKI Project
2021-01-22 11:49 ` Will Deacon
2021-01-22 14:57 ` Rachel Sibley
2021-01-22 19:38 ` Rachel Sibley [this message]
2021-01-22 19:50 ` Will Deacon
2021-01-22 20:30 ` Rachel Sibley
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=f9d423db-eb19-79b1-1ce1-32e6a8adbe0e@redhat.com \
--to=rasibley@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=cki-project@redhat.com \
--cc=jstancek@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=liwang@redhat.com \
--cc=mm-qe@redhat.com \
--cc=skt-results-master@redhat.com \
--cc=will@kernel.org \
--cc=xiawu@redhat.com \
/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).