Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: CKI Project <cki-project@redhat.com>
Cc: Rachel Sibley <rasibley@redhat.com>, Baoquan He <bhe@redhat.com>,
	catalin.marinas@arm.com, Memory Management <mm-qe@redhat.com>,
	skt-results-master@redhat.com, Xiaowu Wu <xiawu@redhat.com>,
	Jan Stancek <jstancek@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 11:49:23 +0000	[thread overview]
Message-ID: <20210122114923.GA24010@willie-the-truck> (raw)
In-Reply-To: <cki.2D3735B145.0JO2GWLYHE@redhat.com>

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?

Thanks,

Will

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-01-22 11:51 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 [this message]
2021-01-22 14:57   ` Rachel Sibley
2021-01-22 19:38     ` Rachel Sibley
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=20210122114923.GA24010@willie-the-truck \
    --to=will@kernel.org \
    --cc=bhe@redhat.com \
    --cc=catalin.marinas@arm.com \
    --cc=cki-project@redhat.com \
    --cc=jstancek@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mm-qe@redhat.com \
    --cc=rasibley@redhat.com \
    --cc=skt-results-master@redhat.com \
    --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