❌ FAIL (MISSED 5 of 41): Test report for for-kernelci (6.16.0-rc5, upstream-arm-next, ec480130)

❌ FAIL (MISSED 5 of 41): Test report for for-kernelci (6.16.0-rc5, upstream-arm-next, ec480130)

[cki-project]

Hi, we tested your kernel and here are the results:

    Overall result: FAILED
             Merge: OK
           Compile: OK
              Test: FAILED


Kernel information:
    Commit message: Merge branches 'for-next/core' and 'for-next/fixes' into for-kernelci

You can find all the details about the test run at
    https://datawarehouse.cki-project.org/kcidb/checkouts/redhat:1914252947

One or more kernel tests failed:
    Unrecognized or new issues:
        Boot test
             aarch64
                   Logs: https://datawarehouse.cki-project.org/kcidb/tests/redhat:1914252947-aarch64-kernel_upt_13
                   Non-passing ran subtests:
                       ❌ FAIL Panic
        selinux-policy: serge-testsuite
             aarch64
                   Logs: https://datawarehouse.cki-project.org/kcidb/tests/redhat:1914252947-aarch64-kernel_upt_24
                   Non-passing ran subtests:
                       ❌ FAIL Test
        stress: stress-ng - memory
             aarch64
                   Logs: https://datawarehouse.cki-project.org/kcidb/tests/redhat:1914252947-aarch64-kernel_upt_8
                   Non-passing ran subtests:
                       ❌ FAIL /10_avc_check

    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]


Tests that were not ran because of internal issues:
    Reboot test [aarch64]
    Storage - blktests - throtl [aarch64]
    Storage - blktests - ublk [aarch64]
    stress: stress-ng - cpu-cache [aarch64]
    stress: stress-ng - memory [aarch64]


If you find a failure unrelated to your changes, please ask the test maintainer to review it.
This will prevent the failures from being incorrectly reported in the future.

Please reply to this email if you have any questions about the tests that we
ran or if you have any suggestions on how to make future tests more effective.

        ,-.   ,-.
       ( C ) ( K )  Continuous
        `-',-.`-'   Kernel
          ( I )     Integration
           `-'
______________________________________________________________________________

Re: ❌ FAIL (MISSED 5 of 41): Test report for for-kernelci (6.16.0-rc5, upstream-arm-next, ec480130)

[Will Deacon]

On Tue, Jul 08, 2025 at 09:23:02PM -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 branches 'for-next/core' and 'for-next/fixes' into for-kernelci
> 
> You can find all the details about the test run at
>     https://datawarehouse.cki-project.org/kcidb/checkouts/redhat:1914252947
> 
> One or more kernel tests failed:
>     Unrecognized or new issues:
>         Boot test
>              aarch64
>                    Logs: https://datawarehouse.cki-project.org/kcidb/tests/redhat:1914252947-aarch64-kernel_upt_13
>                    Non-passing ran subtests:
>                        ❌ FAIL Panic

Yikes, a panic! Unfortunately, I can't seem to find any more details:

  - test_kernel_panic.log contains:

      "Test aborted due to a kernel panic, please review the console.log file."

  - console.log is empty

  - The other output files don't contain a panic message

Please can a CKI person dig up the panic message for me? I guess it died
really early or something.

Cheers,

Will

Re: ❌ FAIL (MISSED 5 of 41): Test report for for-kernelci (6.16.0-rc5, upstream-arm-next, ec480130)

[Will Deacon]

On Wed, Jul 09, 2025 at 01:38:52PM +0200, Bruno Goncalves wrote:
> On Wed, 9 Jul 2025 at 13:30, Ondrej Mosnacek <omosnace@redhat.com> wrote:
> > On Wed, Jul 9, 2025 at 1:24 PM Will Deacon <will@kernel.org> wrote:
> > > On Tue, Jul 08, 2025 at 09:23:02PM -0000, cki-project@redhat.com wrote:
> > > > One or more kernel tests failed:
> > > >     Unrecognized or new issues:
> > > >         Boot test
> > > >              aarch64
> > > >                    Logs: https://datawarehouse.cki-project.org/kcidb/tests/redhat:1914252947-aarch64-kernel_upt_13
> > > >                    Non-passing ran subtests:
> > > >                        ❌ FAIL Panic
> > >
> > > Yikes, a panic! Unfortunately, I can't seem to find any more details:
> > >
> > >   - test_kernel_panic.log contains:
> > >
> > >       "Test aborted due to a kernel panic, please review the console.log file."
> > >
> > >   - console.log is empty
> > >
> > >   - The other output files don't contain a panic message
> > >
> > > Please can a CKI person dig up the panic message for me? I guess it died
> > > really early or something.
> >
> > not actually a CKI person and not sure what happened to the
> > console.log, but as a RH employee I can click through to the actual
> > Beaker job and the console.log is available there. Pasting the
> > relevant snippet below:
> 
> Thanks Ondrej,
> 
> adding more context, the panic happened when rebooting the machine,
> after the upstream arm kernel was installed, but it was not running.
> This panic happened
>  on the fedora kernel.

Thanks Ondrej, Bruno. I won't hold up the arm64 fixes pull request on
this, then.

Cheers,

Will