From: "kernelci.org bot" <bot@kernelci•org>
To: linux-next@vger•kernel.org
Subject: next/pending-fixes boot: 273 boots: 4 failed, 263 passed with 5 offline, 1 untried/unknown (v5.4-rc8-126-g232aa1d5e73c)
Date: Thu, 21 Nov 2019 02:23:56 -0800 (PST) [thread overview]
Message-ID: <5dd665bc.1c69fb81.56f7d.ae31@mx.google.com> (raw)
next/pending-fixes boot: 273 boots: 4 failed, 263 passed with 5 offline, 1 untried/unknown (v5.4-rc8-126-g232aa1d5e73c)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/pending-fixes/kernel/v5.4-rc8-126-g232aa1d5e73c/
Full Build Summary: https://kernelci.org/build/next/branch/pending-fixes/kernel/v5.4-rc8-126-g232aa1d5e73c/
Tree: next
Branch: pending-fixes
Git Describe: v5.4-rc8-126-g232aa1d5e73c
Git Commit: 232aa1d5e73ce18369cd98f2ddc3c14d6dbeb28b
Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 100 unique boards, 27 SoC families, 28 builds out of 216
Boot Regressions Detected:
arm:
multi_v7_defconfig:
gcc-8:
am335x-boneblack:
lab-baylibre: new failure (last pass: v5.4-rc8-85-g0632e899eb04)
multi_v7_defconfig+CONFIG_SMP=n:
gcc-8:
am335x-boneblack:
lab-baylibre: new failure (last pass: v5.4-rc8-85-g0632e899eb04)
sun8i-h2-plus-orangepi-r1:
lab-baylibre: new failure (last pass: v5.4-rc8-95-g08504765f773)
Boot Failures Detected:
arm64:
defconfig:
gcc-8:
msm8998-mtp: 1 failed lab
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8:
juno-r2: 1 failed lab
arm:
multi_v7_defconfig:
gcc-8:
am335x-boneblack: 1 failed lab
multi_v7_defconfig+CONFIG_SMP=n:
gcc-8:
am335x-boneblack: 1 failed lab
Offline Platforms:
arm:
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
exynos_defconfig:
gcc-8
exynos5800-peach-pi: 1 offline lab
---
For more info write to <info@kernelci•org>
reply other threads:[~2019-11-21 10:24 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=5dd665bc.1c69fb81.56f7d.ae31@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