From: "kernelci.org bot" <bot@kernelci•org>
To: linux-next@vger•kernel.org
Subject: next/master boot: 99 boots: 7 failed, 91 passed with 1 conflict (next-20200302)
Date: Mon, 02 Mar 2020 05:02:31 -0800 (PST) [thread overview]
Message-ID: <5e5d03e7.1c69fb81.82d6c.a613@mx.google.com> (raw)
next/master boot: 99 boots: 7 failed, 91 passed with 1 conflict (next-20200302)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20200302/
Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20200302/
Tree: next
Branch: master
Git Describe: next-20200302
Git Commit: b56557c8e5210c25b008da636ef804b228967aa6
Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 56 unique boards, 12 SoC families, 20 builds out of 329
Boot Regressions Detected:
arm:
sama5_defconfig:
gcc-8:
at91-sama5d4_xplained:
lab-baylibre: failing since 13 days (last pass: next-20200214 - first fail: next-20200217)
arm64:
defconfig:
gcc-8:
meson-gxl-s805x-libretech-ac:
lab-baylibre: new failure (last pass: next-20200228)
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8:
meson-gxbb-p200:
lab-baylibre: new failure (last pass: next-20200228)
Boot Failures Detected:
arm:
sama5_defconfig:
gcc-8:
at91-sama5d4_xplained: 1 failed lab
arm64:
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8:
meson-gxbb-p200: 1 failed lab
defconfig+CONFIG_RANDOMIZE_BASE=y:
gcc-8:
rk3399-puma-haikou: 1 failed lab
defconfig:
gcc-8:
meson-gxl-s805x-libretech-ac: 1 failed lab
rk3399-puma-haikou: 1 failed lab
Conflicting Boot Failure Detected: (These likely are not failures as other labs are reporting PASS. Needs review.)
arm64:
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
meson-gxl-s905x-libretech-cc:
lab-baylibre: PASS (gcc-8)
lab-clabbe: FAIL (gcc-8)
---
For more info write to <info@kernelci•org>
reply other threads:[~2020-03-02 13:02 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=5e5d03e7.1c69fb81.82d6c.a613@mx.google.com \
--to=bot@kernelci$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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