From: Mark Brown <broonie@kernel.org>
To: Nick Desaulniers <ndesaulniers@google.com>,
Nathan Chancellor <natechancellor@gmail.com>,
Tri Vo <trong@google.com>
Cc: kernel-build-reports@lists.linaro.org,
linux-arm-kernel@lists.infradead.org, linux-next@vger.kernel.org,
Matt Hart <matthew.hart@linaro.org>,
Kevin Hilman <khilman@baylibre.com>
Subject: Re: next/master boot: 256 boots: 6 failed, 177 passed with 72 offline, 1 conflict (next-20190805)
Date: Mon, 5 Aug 2019 15:24:23 +0100 [thread overview]
Message-ID: <20190805142423.GG6432@sirena.org.uk> (raw)
In-Reply-To: <5d482ab9.1c69fb81.684ee.d95e@mx.google.com>
[-- Attachment #1: Type: text/plain, Size: 850 bytes --]
On Mon, Aug 05, 2019 at 06:10:17AM -0700, kernelci.org bot wrote:
> arm64:
> defconfig+CONFIG_CPU_BIG_ENDIAN=y:
> clang-8:
> meson-gxl-s805x-p241: 1 failed lab
> meson-gxl-s905x-khadas-vim: 1 failed lab
> meson-gxl-s905x-libretech-cc: 1 failed lab
We're still seeing failures with all clang builds failing to understand
the executable format of /init in big endian arm64 builds; GCC builds of
the same configuration boot successfully. This has been going on for
about as long as we've been trying to boot clang builds AFAICT, it's a
huge proportion of the failures we're seeing in -next.
I did notice one similar failure for v7 GCC today:
https://kernelci.org/boot/id/5d4807f559b514d97f31b28e/
which is also happening for other trees so that one at least looks
suspiciously like infrastructure.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next parent reply other threads:[~2019-08-05 14:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5d482ab9.1c69fb81.684ee.d95e@mx.google.com>
2019-08-05 14:24 ` Mark Brown [this message]
2019-08-05 13:10 next/master boot: 256 boots: 6 failed, 177 passed with 72 offline, 1 conflict (next-20190805) kernelci.org bot
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=20190805142423.GG6432@sirena.org.uk \
--to=broonie@kernel.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=khilman@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=matthew.hart@linaro.org \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=trong@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;
as well as URLs for NNTP newsgroup(s).