From: Catalin Marinas <catalin.marinas@arm.com>
To: cki-project@redhat.com
Cc: will@kernel.org, linux-arm-kernel@lists.infradead.org,
jbastian@redhat.com
Subject: Re: ❌ FAIL (MISSED 13 of 105): Test report for for-kernelci (6.6.0-rc7, arm-next, 8de1e7af)
Date: Fri, 27 Oct 2023 11:21:06 +0100 [thread overview]
Message-ID: <ZTuPEjf9el8ZBY1J@arm.com> (raw)
In-Reply-To: <21083.123102704410900155@us-mta-532.us.mimecast.lan>
On Fri, Oct 27, 2023 at 08:41:08AM -0000, cki-project@redhat.com wrote:
> Hi, we tested your kernel and here are the results:
>
> Overall result: FAILED
> Merge: OK
> Compile: OK
> Test: FAILED
>
>
> Kernel information:
> Commit message: Merge branch 'for-next/core' into for-kernelci
>
> You can find all the details about the test run at
> https://datawarehouse.cki-project.org/kcidb/checkouts/111504
>
> One or more kernel tests failed:
> Unrecognized or new issues:
> aarch64 - stress: stress-ng - memory
> Logs: https://datawarehouse.cki-project.org/kcidb/tests/10075580
> Non-passing subtests:
> ❌ FAIL /10_avc_check
> aarch64 - stress: stress-ng - memory
> Logs: https://datawarehouse.cki-project.org/kcidb/tests/10075594
> Non-passing subtests:
> ❌ FAIL /10_avc_check
These don't seem related to the kernel (or at least not to the arm64
for-kernelci branch). Could it be something with the SELinux policy
setup that stressng trips over (the avc log mentions secretmem)?
Thanks.
--
Catalin
_______________________________________________
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:[~2023-10-27 10:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 8:41 ❌ FAIL (MISSED 13 of 105): Test report for for-kernelci (6.6.0-rc7, arm-next, 8de1e7af) cki-project
2023-10-27 10:21 ` Catalin Marinas [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=ZTuPEjf9el8ZBY1J@arm.com \
--to=catalin.marinas@arm.com \
--cc=cki-project@redhat.com \
--cc=jbastian@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.