linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: cki-project@redhat.com
Cc: will@kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: ❌ FAIL: Test report for for-kernelci (6.10.0-rc2, arm-next, 8867bbd4)
Date: Wed, 5 Jun 2024 18:06:18 +0100	[thread overview]
Message-ID: <ZmCbClzlPTuUXX_i@arm.com> (raw)
In-Reply-To: <54578.124060509220604038@us-mta-660.us.mimecast.lan>

On Wed, Jun 05, 2024 at 01:22:05PM -0000, cki-project@redhat.com wrote:
> Hi, we tested your kernel and here are the results:
> 
>     Overall result: FAILED
>              Merge: OK
>            Compile: FAILED
> 
> 
> Kernel information:
>     Commit message: mm: arm64: Fix the out-of-bounds issue in contpte_clear_young_dirty_ptes
> 
> You can find all the details about the test run at
>     https://datawarehouse.cki-project.org/kcidb/checkouts/redhat:1319489611
> 
> One or more kernel builds failed:
>     Unrecognized or new issues:
>          aarch64 - https://datawarehouse.cki-project.org/kcidb/builds/redhat:1319489611-aarch64-kernel

This doesn't look like an arm64 issue:

00:00:12   HOSTLD  /builds/7025259652/workdir/tools/bpf/resolve_btfids/resolve_btfids-in.o
00:00:12   LINK     resolve_btfids
00:00:12   LDS     scripts/module.lds
00:00:12   CC      init/main.o
00:00:12   HOSTCC  usr/gen_init_cpio
00:00:12 make[5]: *** No rule to make target 'certs/rhel.pem', needed by 'certs/x509_certificate_list'.  Stop.
00:00:12 make[5]: *** Waiting for unfinished jobs....
00:00:12   CC      certs/system_keyring.o
00:00:12   CC      init/do_mounts.o
00:00:12   CC      init/do_mounts_initrd.o
00:00:12   CC      ipc/compat.o
--
00:00:13   HDRTEST usr/include/asm-generic/hugetlb_encode.h
00:00:13   HDRTEST usr/include/asm-generic/int-l64.h
00:00:13   HDRTEST usr/include/asm-generic/int-ll64.h
00:00:13   AS      arch/arm64/lib/copy_to_user.o
00:00:13   HDRTEST usr/include/asm-generic/ioctl.h
00:00:13 make[4]: *** [scripts/Makefile.build:485: certs] Error 2
00:00:13 make[4]: *** Waiting for unfinished jobs....
00:00:13   CC      arch/arm64/lib/csum.o
00:00:13   HDRTEST usr/include/asm-generic/ioctls.h
00:00:13   HDRTEST usr/include/asm-generic/ipcbuf.h
00:00:13   CC      block/fops.o
--
00:25:07   CC [M]  drivers/gpu/drm/amd/amdgpu/../display/modules/hdcp/hdcp2_transition.o
00:25:08   LD [M]  drivers/gpu/drm/nouveau/nouveau.o
00:25:09   LD [M]  drivers/gpu/drm/amd/amdgpu/amdgpu.o
00:25:11   AR      drivers/gpu/built-in.a
00:25:11   AR      drivers/built-in.a
00:25:11 make[3]: *** [Makefile:1934: .] Error 2
00:25:11 make[2]: *** [scripts/Makefile.package:148: tar-install] Error 2
00:25:11 make[1]: *** [/builds/7025259652/workdir/Makefile:1555: targz-pkg] Error 2
00:25:11 make: *** [Makefile:240: __sub-make] Error 2

-- 
Catalin

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2024-06-05 17:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-05 13:22 ❌ FAIL: Test report for for-kernelci (6.10.0-rc2, arm-next, 8867bbd4) cki-project
2024-06-05 17:06 ` 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=ZmCbClzlPTuUXX_i@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=cki-project@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).