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: catalin.marinas@arm.com, Memory Management <mm-qe@redhat.com>,
	Jan Stancek <jstancek@redhat.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: ❌ FAIL: Test report for kernel 5.7.0-rc5-51f14e2.cki (arm-next)
Date: Wed, 13 May 2020 07:12:27 +0100	[thread overview]
Message-ID: <20200513060321.GA17433@willie-the-truck> (raw)
In-Reply-To: <cki.495C39BD1A.T35Z6VDJPY@redhat.com>

Hi CKI folks,

On Wed, May 13, 2020 at 03:01:36AM -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: 51f14e2c02e8 - Merge branch 'for-next/core' 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://cki-artifacts.s3.us-east-2.amazonaws.com/index.html?prefix=datawarehouse/2020/05/12/564910
> 
> One or more kernel tests failed:
> 
>     aarch64:
>      ❌ LTP

[...]

>     Host 2:
>        ✅ Boot test
>        ✅ Podman system integration test - as root
>        ✅ Podman system integration test - as user
>        ❌ LTP

I'm struggling a bit with this one, please can you confirm that it's not
an issue on your end? The failures are related to /dev/cpuset:

  mem.c:760: BROK: mount /dev/cpuset: EBUSY (16)
  ...
  safe_macros.c:172: BROK: mem.c:750: mkdir(/dev/cpuset,0777) failed: EEXIST (17)

  https://cki-artifacts.s3.us-east-2.amazonaws.com/datawarehouse/2020/05/12/564910/LTP/aarch64_2_ltp_mm.fail.log

But we haven't been anywhere near that in the arm64 tree afaik.

Cheers,

Will

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

  reply	other threads:[~2020-05-13  6:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-13  3:01 ❌ FAIL: Test report for kernel 5.7.0-rc5-51f14e2.cki (arm-next) CKI Project
2020-05-13  6:12 ` Will Deacon [this message]
2020-05-13 10:19   ` Veronika Kabatova
2020-05-13 15:40     ` Jan Stancek
2020-05-13 15:51       ` ❌ FAIL: Test report for kernel?5.7.0-rc5-51f14e2.cki (arm-next) Tejun Heo

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=20200513060321.GA17433@willie-the-truck \
    --to=will@kernel.org \
    --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 \
    /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