From: "kernelci.org bot" <bot@kernelci.org>
To: linux-next@vger.kernel.org
Subject: next/master boot: 162 boots: 9 failed, 147 passed with 5 offline, 1 untried/unknown (next-20200210)
Date: Mon, 10 Feb 2020 01:15:33 -0800 (PST) [thread overview]
Message-ID: <5e411f35.1c69fb81.4bb2e.7e38@mx.google.com> (raw)
next/master boot: 162 boots: 9 failed, 147 passed with 5 offline, 1 untried/unknown (next-20200210)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20200210/
Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20200210/
Tree: next
Branch: master
Git Describe: next-20200210
Git Commit: 2981de746b18227892dfbda7b70c099077c4580d
Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 95 unique boards, 24 SoC families, 22 builds out of 184
Boot Regressions Detected:
arc:
hsdk_defconfig:
gcc-8:
hsdk:
lab-baylibre: new failure (last pass: next-20200207)
arm64:
defconfig:
gcc-8:
apq8016-sbc:
lab-bjorn: failing since 9 days (last pass: next-20200130 - first fail: next-20200131)
bcm2837-rpi-3-b:
lab-baylibre: new failure (last pass: next-20200207)
meson-axg-s400:
lab-baylibre-seattle: new failure (last pass: next-20200207)
meson-gxl-s805x-libretech-ac:
lab-baylibre: new failure (last pass: next-20200207)
meson-gxl-s905x-libretech-cc:
lab-clabbe: new failure (last pass: next-20200207)
sun50i-a64-bananapi-m64:
lab-clabbe: new failure (last pass: next-20200207)
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8:
meson-axg-s400:
lab-baylibre-seattle: new failure (last pass: next-20200207)
meson-gxl-s805x-p241:
lab-baylibre: failing since 2 days (last pass: next-20200206 - first fail: next-20200207)
meson-gxm-q200:
lab-baylibre: new failure (last pass: next-20200207)
sun50i-a64-pine64-plus:
lab-baylibre: new failure (last pass: next-20200207)
Boot Failures Detected:
arm:
multi_v7_defconfig:
gcc-8:
bcm2836-rpi-2-b: 1 failed lab
arm64:
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8:
juno-r2: 1 failed lab
meson-gxl-s805x-p241: 1 failed lab
meson-gxm-q200: 1 failed lab
sun50i-a64-pine64-plus: 1 failed lab
defconfig:
gcc-8:
apq8016-sbc: 1 failed lab
bcm2837-rpi-3-b: 1 failed lab
meson-gxl-s805x-libretech-ac: 1 failed lab
msm8998-mtp: 1 failed lab
Offline Platforms:
arm:
qcom_defconfig:
gcc-8
qcom-apq8064-cm-qs600: 1 offline lab
multi_v7_defconfig:
gcc-8
imx6dl-wandboard_dual: 1 offline lab
qcom-apq8064-cm-qs600: 1 offline lab
arm64:
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8
meson-axg-s400: 1 offline lab
defconfig:
gcc-8
meson-axg-s400: 1 offline lab
---
For more info write to <info@kernelci.org>
reply other threads:[~2020-02-10 9:15 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=5e411f35.1c69fb81.4bb2e.7e38@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).