From: "Guillaume Tucker" <guillaume.tucker@collabora.com>
To: kernelci@groups.io, tkjos@google.com
Subject: Re: many kernelci errors on Android branches
Date: Mon, 2 May 2022 19:54:21 +0100 [thread overview]
Message-ID: <b788578e-65e5-4194-c130-e4252ce15813@collabora.com> (raw)
In-Reply-To: <CAHRSSEyjupT5aq2Rs_k1rBrnJx_0RTN7O=A5Up3Cy+M--c7JHg@mail.gmail.com>
On 29/04/2022 23:55, Todd Kjos via groups.io wrote:
> We've been seeing massive failures in some of our branches lately that
> don't seem to correlate to changes in the kernel source.
This was due to some subtle side-effect in a configuration change
that went into production last week to build kselftest with any
kernel config. A fix for that has been rolled out today to only
build kselftest with kernel versions v5.10 or more recent. The
stable and Android trees are back to normal now.
> For example, all android12-5.4 builds are flagged as failing. The actual
> builds seem to work in most cases, but they are apparently flagged as
> failures because of the error in the kselftest log
> <https://storage.kernelci.org/android/android12-5.4/ASB-2022-04-05_12-5.4-6-g99f7ebe8ce34/arm64/gki_defconfig/gcc-10/logs/kselftest.log>
> :
>
> #
> # 2022-04-25T23:25:44.634974
> #
> # make KBUILD_BUILD_USER=KernelCI FORMAT=.xz ARCH=arm64 HOSTCC=gcc
> CROSS_COMPILE=aarch64-linux-gnu-
> CROSS_COMPILE_COMPAT=arm-linux-gnueabihf- CC="ccache
> aarch64-linux-gnu-gcc" O=/tmp/kci/linux/build
> -C/tmp/kci/linux/tools/testing/selftests -j4 gen_tar
> #
> make: Entering directory '/tmp/kci/linux/tools/testing/selftests'
> make: *** No rule to make target 'gen_tar'. Stop.
> make: Leaving directory '/tmp/kci/linux/tools/testing/selftests'
The gen_tar make target was added a bit before v5.10. So I can
confirm it's entirely a KernelCI build configuration issue and
there's nothing wrong with the kernel code.
> This started on April 25 and the 1 change since the passing builds could
> not have caused the issue (change to symbol list which isn't used for
> kernelci builds).
>
> Any suggestions on how to fix this?
Sorry for the inconvenience.
Best wishes,
Guillaume
next prev parent reply other threads:[~2022-05-02 18:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 22:55 many kernelci errors on Android branches Todd Kjos
2022-05-02 18:54 ` Guillaume Tucker [this message]
2022-05-02 18:55 ` 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=b788578e-65e5-4194-c130-e4252ce15813@collabora.com \
--to=guillaume.tucker@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