From: "kernelci.org bot" <bot@kernelci.org>
To: linux-next@vger.kernel.org
Subject: next/master boot: 228 boots: 58 failed, 161 passed with 8 offline, 1 conflict (next-20191107)
Date: Thu, 07 Nov 2019 09:41:30 -0800 (PST) [thread overview]
Message-ID: <5dc4574a.1c69fb81.7fde.f733@mx.google.com> (raw)
next/master boot: 228 boots: 58 failed, 161 passed with 8 offline, 1 conflict (next-20191107)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20191107/
Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20191107/
Tree: next
Branch: master
Git Describe: next-20191107
Git Commit: c68c5373c504078cc0e0edc7d5c88b47ca308144
Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 86 unique boards, 24 SoC families, 26 builds out of 216
Boot Failures Detected:
arm:
multi_v7_defconfig+CONFIG_EFI=y+CONFIG_ARM_LPAE=y:
gcc-8:
tegra124-nyan-big: 1 failed lab
arm64:
defconfig:
gcc-8:
apq8016-sbc: 1 failed lab
apq8096-db820c: 1 failed lab
meson-axg-s400: 1 failed lab
meson-g12a-x96-max: 1 failed lab
meson-g12b-odroid-n2: 1 failed lab
meson-g12b-s922x-khadas-vim3: 1 failed lab
meson-gxbb-p200: 1 failed lab
meson-gxl-s805x-libretech-ac: 1 failed lab
meson-gxl-s905x-khadas-vim: 1 failed lab
meson-gxl-s905x-libretech-cc: 3 failed labs
meson-gxm-khadas-vim2: 1 failed lab
meson-gxm-nexbox-a1: 1 failed lab
meson-sm1-khadas-vim3l: 1 failed lab
meson-sm1-sei610: 1 failed lab
msm8998-mtp: 1 failed lab
mt7622-rfb1: 1 failed lab
qcs404-evb-4k: 1 failed lab
r8a7795-salvator-x: 1 failed lab
rk3399-gru-kevin: 1 failed lab
sdm845-db845c: 1 failed lab
sdm845-mtp: 1 failed lab
sun50i-a64-bananapi-m64: 1 failed lab
defconfig+CONFIG_RANDOMIZE_BASE=y:
gcc-8:
meson-axg-s400: 1 failed lab
meson-g12a-x96-max: 1 failed lab
meson-g12b-odroid-n2: 1 failed lab
meson-g12b-s922x-khadas-vim3: 1 failed lab
meson-gxbb-p200: 1 failed lab
meson-gxl-s805x-libretech-ac: 1 failed lab
meson-gxl-s905x-khadas-vim: 1 failed lab
meson-gxl-s905x-libretech-cc: 3 failed labs
meson-gxl-s905x-nexbox-a95x: 1 failed lab
meson-gxm-khadas-vim2: 1 failed lab
meson-gxm-nexbox-a1: 1 failed lab
meson-sm1-khadas-vim3l: 1 failed lab
meson-sm1-sei610: 1 failed lab
mt7622-rfb1: 1 failed lab
r8a7795-salvator-x: 1 failed lab
r8a7796-m3ulcb: 2 failed labs
rk3399-gru-kevin: 1 failed lab
sun50i-a64-bananapi-m64: 1 failed lab
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8:
meson-axg-s400: 1 failed lab
meson-gxbb-p200: 1 failed lab
meson-gxl-s805x-libretech-ac: 1 failed lab
meson-gxl-s905x-khadas-vim: 1 failed lab
meson-gxl-s905x-libretech-cc: 3 failed labs
meson-gxl-s905x-nexbox-a95x: 1 failed lab
meson-gxm-khadas-vim2: 1 failed lab
meson-sm1-khadas-vim3l: 1 failed lab
meson-sm1-sei610: 1 failed lab
r8a7795-salvator-x: 1 failed lab
Offline Platforms:
arm:
sunxi_defconfig:
gcc-8
sun5i-r8-chip: 1 offline lab
sun7i-a20-bananapi: 1 offline lab
multi_v7_defconfig:
gcc-8
qcom-apq8064-cm-qs600: 1 offline lab
sun5i-r8-chip: 1 offline lab
sun7i-a20-bananapi: 1 offline lab
davinci_all_defconfig:
gcc-8
dm365evm,legacy: 1 offline lab
qcom_defconfig:
gcc-8
qcom-apq8064-cm-qs600: 1 offline lab
arm64:
defconfig:
gcc-8
meson-gxl-s905x-nexbox-a95x: 1 offline lab
Conflicting Boot Failure Detected: (These likely are not failures as other labs are reporting PASS. Needs review.)
arm64:
defconfig:
r8a7796-m3ulcb:
lab-collabora: PASS (gcc-8)
lab-baylibre: FAIL (gcc-8)
---
For more info write to <info@kernelci.org>
reply other threads:[~2019-11-07 17:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5dc4574a.1c69fb81.7fde.f733@mx.google.com \
--to=bot@kernelci.org \
--cc=linux-next@vger.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).