❌ FAIL: Test report for for-kernelci (7.3.0-rc4, upstream-arm-next, d820e3ba)
Catalin Marinas
catalin.marinas at arm.com
Thu Oct 15 07:39:36 PDT 2026
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 at arm.com> wrote:
> > On Thu, Oct 15, 2026 at 04:42:05AM -0000, cki-project at 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
More information about the linux-arm-kernel
mailing list