From: Veronika Kabatova <vkabatov@redhat.com>
To: Will Deacon <will@kernel.org>, Jan Stancek <jstancek@redhat.com>,
Memory Management <mm-qe@redhat.com>
Cc: catalin marinas <catalin.marinas@arm.com>,
linux-arm-kernel@lists.infradead.org,
CKI Project <cki-project@redhat.com>
Subject: Re: ❌ FAIL: Test report for kernel 5.7.0-rc5-51f14e2.cki (arm-next)
Date: Wed, 13 May 2020 06:19:43 -0400 (EDT) [thread overview]
Message-ID: <1322199095.22739428.1589365183678.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20200513060321.GA17433@willie-the-truck>
----- Original Message -----
> From: "Will Deacon" <will@kernel.org>
> To: "CKI Project" <cki-project@redhat.com>
> Cc: "catalin marinas" <catalin.marinas@arm.com>, "Memory Management" <mm-qe@redhat.com>, "Jan Stancek"
> <jstancek@redhat.com>, linux-arm-kernel@lists.infradead.org
> Sent: Wednesday, May 13, 2020 8:12:27 AM
> Subject: Re: ❌ FAIL: Test report for kernel 5.7.0-rc5-51f14e2.cki (arm-next)
>
> 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.
>
Hi,
I suspect this is an LTP bug:
https://github.com/linux-test-project/ltp/issues/611
The original issue wasn't manifesting with ksm02 test that failed
though.
@Jan or @Li, can you confirm whether this is the case and we should
disable these tests as well? We've found some hidden kernel bugs with
LTP and I can't see any recent similar upstream failures so I'm hesitant
to mark it as a test bug right away.
Thanks,
Veronika
> Cheers,
>
> 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:[~2020-05-13 10:22 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
2020-05-13 10:19 ` Veronika Kabatova [this message]
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=1322199095.22739428.1589365183678.JavaMail.zimbra@redhat.com \
--to=vkabatov@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=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