From: "kernelci.org bot" <bot@kernelci.org>
To: linux-next@vger.kernel.org
Subject: next/master boot: 257 boots: 8 failed, 237 passed with 8 offline, 2 untried/unknown, 2 conflicts (next-20191028)
Date: Mon, 28 Oct 2019 08:03:08 -0700 (PDT) [thread overview]
Message-ID: <5db7032c.1c69fb81.1a75.aa4e@mx.google.com> (raw)
next/master boot: 257 boots: 8 failed, 237 passed with 8 offline, 2 untried/unknown, 2 conflicts (next-20191028)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20191028/
Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20191028/
Tree: next
Branch: master
Git Describe: next-20191028
Git Commit: 60c1769a45f4b6beddcc48843739d7d41b88dc1c
Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 93 unique boards, 26 SoC families, 28 builds out of 216
Boot Failures Detected:
arm64:
defconfig+CONFIG_RANDOMIZE_BASE=y:
gcc-8:
meson-gxl-s805x-libretech-ac: 1 failed lab
meson-sm1-khadas-vim3l: 1 failed lab
meson-sm1-sei610: 1 failed lab
defconfig:
gcc-8:
apq8096-db820c: 1 failed lab
meson-sm1-khadas-vim3l: 1 failed lab
meson-sm1-sei610: 1 failed lab
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8:
meson-sm1-khadas-vim3l: 1 failed lab
meson-sm1-sei610: 1 failed lab
Offline Platforms:
riscv:
defconfig:
gcc-8
sifive_fu540: 1 offline lab
arm:
multi_v7_defconfig:
gcc-8
qcom-apq8064-cm-qs600: 1 offline lab
sun5i-r8-chip: 1 offline lab
sun7i-a20-bananapi: 1 offline lab
sunxi_defconfig:
gcc-8
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
Conflicting Boot Failures Detected: (These likely are not failures as other labs are reporting PASS. Needs review.)
arm:
exynos_defconfig:
exynos5422-odroidxu3:
lab-collabora: FAIL (gcc-8)
lab-baylibre: PASS (gcc-8)
arm64:
defconfig:
meson-gxl-s905x-libretech-cc:
lab-baylibre-seattle: PASS (gcc-8)
lab-clabbe: FAIL (gcc-8)
lab-baylibre: PASS (gcc-8)
---
For more info write to <info@kernelci.org>
next reply other threads:[~2019-10-28 15:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 15:03 kernelci.org bot [this message]
[not found] <5db7032c.1c69fb81.888b0.b521@mx.google.com>
2019-10-28 17:48 ` next/master boot: 257 boots: 8 failed, 237 passed with 8 offline, 2 untried/unknown, 2 conflicts (next-20191028) Mark Brown
2019-10-28 17:48 ` Mark Brown
2019-10-28 18:40 ` Bjorn Andersson
2019-10-28 18:40 ` Bjorn Andersson
2019-10-28 19:11 ` Mark Brown
2019-10-28 19:11 ` Mark Brown
2019-10-28 20:02 ` Bjorn Andersson
2019-10-28 20:02 ` Bjorn Andersson
2019-10-28 20:14 ` Will Deacon
2019-10-28 20:14 ` Will Deacon
2019-10-28 20:23 ` Mark Brown
2019-10-28 20:23 ` Mark Brown
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=5db7032c.1c69fb81.1a75.aa4e@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.