From: "kernelci.org bot" <bot@kernelci.org>
To: linux-next@vger.kernel.org
Subject: next/master boot: 275 boots: 5 failed, 260 passed with 7 offline, 2 untried/unknown, 1 conflict (next-20191203)
Date: Tue, 03 Dec 2019 01:57:00 -0800 (PST) [thread overview]
Message-ID: <5de6316c.1c69fb81.915d4.b99a@mx.google.com> (raw)
next/master boot: 275 boots: 5 failed, 260 passed with 7 offline, 2 untried/unknown, 1 conflict (next-20191203)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20191203/
Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20191203/
Tree: next
Branch: master
Git Describe: next-20191203
Git Commit: 1ab75b2e415a29dba9aec94f203c6f88dbfc0ba0
Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 101 unique boards, 24 SoC families, 28 builds out of 209
Boot Failures Detected:
arm:
qcom_defconfig:
gcc-8:
qcom-apq8064-cm-qs600: 1 failed lab
multi_v7_defconfig:
gcc-8:
sun8i-h3-libretech-all-h3-cc: 1 failed lab
arm64:
defconfig:
gcc-8:
meson-gxl-s905x-khadas-vim: 1 failed lab
msm8998-mtp: 1 failed lab
rk3399-gru-kevin: 1 failed lab
Offline Platforms:
arm:
exynos_defconfig:
gcc-8
exynos5800-peach-pi: 1 offline lab
davinci_all_defconfig:
gcc-8
dm365evm,legacy: 1 offline lab
sunxi_defconfig:
gcc-8
sun7i-a20-bananapi: 1 offline lab
multi_v7_defconfig:
gcc-8
exynos5800-peach-pi: 1 offline lab
mt7623n-bananapi-bpi-r2: 1 offline lab
sun7i-a20-bananapi: 1 offline lab
arm64:
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8
meson-sm1-khadas-vim3l: 1 offline lab
Conflicting Boot Failure Detected: (These likely are not failures as other labs are reporting PASS. Needs review.)
arm:
multi_v7_defconfig:
imx6q-sabrelite:
lab-baylibre: PASS (gcc-8)
lab-collabora: FAIL (gcc-8)
---
For more info write to <info@kernelci.org>
reply other threads:[~2019-12-03 9:57 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=5de6316c.1c69fb81.915d4.b99a@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).