* Re: next/master boot: 256 boots: 6 failed, 177 passed with 72 offline, 1 conflict (next-20190805)
[not found] <5d482ab9.1c69fb81.684ee.d95e@mx.google.com>
@ 2019-08-05 14:24 ` Mark Brown
0 siblings, 0 replies; only message in thread
From: Mark Brown @ 2019-08-05 14:24 UTC (permalink / raw)
To: Nick Desaulniers, Nathan Chancellor, Tri Vo
Cc: Kevin Hilman, linux-next, Matt Hart, linux-arm-kernel,
kernel-build-reports
[-- Attachment #1.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 #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] only message in thread