From: Catalin Marinas <catalin.marinas@arm.com>
To: Ondrej Mosnacek <omosnace@redhat.com>
Cc: cki-project@redhat.com, linux-arm-kernel@lists.infradead.org,
mmalik@redhat.com, will@kernel.org
Subject: Re: ❌ FAIL: Test report for for-kernelci (7.3.0-rc4, upstream-arm-next, d820e3ba)
Date: Thu, 15 Oct 2026 15:39:36 +0100 [thread overview]
Message-ID: <atDlqCgB72yHmDHN@arm.com> (raw)
In-Reply-To: <CAFqZXNsV_P_jxt9ZVYBYdh9vuFDPrsCh-Ch7niccns0WRgbs8A@mail.gmail.com>
On Thu, Oct 15, 2026 at 02:39:43PM +0200, Ondrej Mosnacek wrote:
> On Thu, Oct 15, 2026 at 1:31 PM Catalin Marinas <catalin.marinas@arm.com> wrote:
> > On Thu, Oct 15, 2026 at 04:42:05AM -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/fw-rmi' into for-next/core
> > >
> > > You can find all the details about the test run at
> > > https://datawarehouse.cki-project.org/kcidb/checkouts/redhat:2947827228
> > >
> > > One or more kernel tests failed:
> > > Unrecognized or new issues:
> > > selinux-policy: serge-testsuite
> > > aarch64
> > > Logs: https://datawarehouse.cki-project.org/kcidb/tests/redhat:2947827228_aarch64_kernel_kcidb_tool_1200470666_8
> > > Non-passing ran subtests:
> > > ❌ FAIL Test
> > >
> > > We also see the following known issues which are not related to your changes:
> > > Issue: [upstream] Hardware - Firmware test suite - auto-waive failures
> > > URL: https://gitlab.com/cki-project/infrastructure/-/issues/779
> > > Affected tests:
> > > Hardware - Firmware test suite [aarch64]
> >
> > Is this another infrastructure issue? From the logs:
> >
> > + nft -f /root/selinux-testsuite/tests/sctp/nftables-flush
> > /root/selinux-testsuite/tests/sctp/nftables-flush:1:17-24: Error: Could not process rule: No such file or directory
> > delete table ip security
>
> the above is not the source of the failure, that part is expected to
> fail normally.
I have yet to learn how to look at these logs properly ;).
> The problem is the failing binder/test, which is a
> recent regression in mainline that I'm currently investigating. I
> created DW issue https://datawarehouse.cki-project.org/issue/11475 to
> waive these failures for now. I'll update it with a proper link once I
> report the bug / post a fix.
Thanks, good to know. So it's unlikely to be something I pushed into the
for-kernelci branch.
--
Catalin
prev parent reply other threads:[~2026-10-15 14:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 4:42 ❌ FAIL: Test report for for-kernelci (7.3.0-rc4, upstream-arm-next, d820e3ba) cki-project
2026-10-15 11:24 ` Catalin Marinas
[not found] ` <CAFqZXNsV_P_jxt9ZVYBYdh9vuFDPrsCh-Ch7niccns0WRgbs8A@mail.gmail.com>
2026-10-15 14:39 ` 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=atDlqCgB72yHmDHN@arm.com \
--to=catalin.marinas@arm.com \
--cc=cki-project@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mmalik@redhat.com \
--cc=omosnace@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 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.