public inbox for kernelci@lists.linux.dev
 help / color / mirror / Atom feed
From: denys.f@collabora.com
To: kernelci@groups.io, tkjos@google.com
Subject: Re: kernelci failures due to "pahole" missing
Date: Tue, 03 May 2022 07:58:08 +0300	[thread overview]
Message-ID: <f91a21bd782f3988cb6988ff96558dda036ca16f.camel@collabora.com> (raw)
In-Reply-To: <CAHRSSEwMoYQz2ua+PmFRcWSXJREUtrsKCFdivDJ+XdJP9Di_MQ@mail.gmail.com>

Hi, 

We are testing in staging fix for that:
https://github.com/kernelci/kernelci-core/pull/1158

Also i noticed in some cases lz4 package required for this test,
so added it too.

Best regards,
Denys

On Fri, 2022-04-29 at 15:22 -0700, Todd Kjos via groups.io wrote:
> We have a bunch of Android kernel test failures due to missing
> "pahole" in
> the build environment (example android13-5.15 gki_defconfig
> <https://storage.kernelci.org/android/android13-5.15/ASB-2022-04-05_13-5.15-1515-g7a68c2c45139/arm64/gki_defconfig/gcc-10/logs/kernel.log
> >
> ):
> 
> 
>   LD      vmlinux.o
>   MODPOST vmlinux.symvers
>   MODINFO modules.builtin.modinfo
>   GEN     modules.builtin
> BTF: .tmp_vmlinux.btf: pahole (pahole) is not available
> Failed to generate BTF for vmlinux
> Try to disable CONFIG_DEBUG_INFO_BTF
> make[1]: *** [/tmp/kci/linux/Makefile:1247: vmlinux] Error 1
> make[1]: Leaving directory '/tmp/kci/linux/build'
> make: *** [Makefile:237: __sub-make] Error 2
> make: Leaving directory '/tmp/kci/linux'
> 
> Would it be possible to get pahole added to the build environments
> used to
> build android kernels?
> 
> -Todd
> 
> 
> 
> 
> 



  reply	other threads:[~2022-05-03  4:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-29 22:22 kernelci failures due to "pahole" missing Todd Kjos
2022-05-03  4:58 ` denys.f [this message]
2022-05-03 14:45   ` Todd Kjos
2022-05-04  9:06     ` Denys Fedoryshchenko
     [not found]     ` <16EBDBAB78C06CE6.10903@groups.io>
2022-05-05  5:23       ` Denys Fedoryshchenko
2022-05-10  7:20         ` Denys Fedoryshchenko
2022-05-10 17:53           ` Todd Kjos
2022-05-10 19:50             ` Denys Fedoryshchenko
2022-06-28 19:16               ` Todd Kjos
2022-06-29 11:27                 ` Denys Fedoryshchenko
2022-07-08 17:02                   ` Todd Kjos
2022-07-12  9:48                     ` Denys Fedoryshchenko
2022-07-13 17:32                       ` Todd Kjos
2022-07-13 17:40                         ` Denys Fedoryshchenko
2022-07-13 17:45                           ` Todd Kjos
2022-09-06 12:53                             ` Denys Fedoryshchenko
2022-09-06 15:35                               ` Todd Kjos

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=f91a21bd782f3988cb6988ff96558dda036ca16f.camel@collabora.com \
    --to=denys.f@collabora.com \
    --cc=kernelci@groups.io \
    --cc=tkjos@google.com \
    /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