From: "kernelci.org bot" <bot@kernelci.org>
To: linux-next@vger.kernel.org
Subject: next/pending-fixes boot: 232 boots: 11 failed, 221 passed (v5.4-rc1-197-gcd6b2766cc1d)
Date: Tue, 01 Oct 2019 23:41:31 -0700 (PDT) [thread overview]
Message-ID: <5d94469b.1c69fb81.8d7f4.7cf9@mx.google.com> (raw)
next/pending-fixes boot: 232 boots: 11 failed, 221 passed (v5.4-rc1-197-gcd6b2766cc1d)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/pending-fixes/kernel/v5.4-rc1-197-gcd6b2766cc1d/
Full Build Summary: https://kernelci.org/build/next/branch/pending-fixes/kernel/v5.4-rc1-197-gcd6b2766cc1d/
Tree: next
Branch: pending-fixes
Git Describe: v5.4-rc1-197-gcd6b2766cc1d
Git Commit: cd6b2766cc1d12e6342a6f09626ac82974aecc50
Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 55 unique boards, 16 SoC families, 22 builds out of 214
Boot Regressions Detected:
arm:
bcm2835_defconfig:
gcc-8:
bcm2836-rpi-2-b:
lab-collabora: failing since 2 days (last pass: v5.3-12689-gd20eeb14322b - first fail: v5.3-13311-g8d0cc3a7f82f)
bcm2837-rpi-3-b:
lab-baylibre: failing since 2 days (last pass: v5.3-12689-gd20eeb14322b - first fail: v5.3-13311-g8d0cc3a7f82f)
arm64:
defconfig:
gcc-8:
apq8096-db820c:
lab-bjorn: failing since 1 day (last pass: v5.3-13311-g8d0cc3a7f82f - first fail: v5.4-rc1-91-gae083b2a11c7)
defconfig+kselftest:
gcc-8:
meson-gxl-s805x-libretech-ac:
lab-baylibre: new failure (last pass: v5.4-rc1-91-gae083b2a11c7)
Boot Failures Detected:
arm:
multi_v7_defconfig+kselftest:
gcc-8:
bcm2836-rpi-2-b: 1 failed lab
rk3288-rock2-square: 1 failed lab
bcm2835_defconfig:
gcc-8:
bcm2836-rpi-2-b: 1 failed lab
bcm2837-rpi-3-b: 1 failed lab
arm64:
defconfig:
gcc-8:
apq8096-db820c: 1 failed lab
defconfig+kselftest:
gcc-8:
meson-gxl-s805x-libretech-ac: 1 failed lab
qcom-qdf2400: 1 failed lab
r8a7795-salvator-x: 1 failed lab
r8a7796-m3ulcb: 2 failed labs
rk3399-puma-haikou: 1 failed lab
---
For more info write to <info@kernelci.org>
reply other threads:[~2019-10-02 6: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=5d94469b.1c69fb81.8d7f4.7cf9@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).