From: "kernelci.org bot" <bot@kernelci.org>
To: linux-next@vger.kernel.org
Subject: next/pending-fixes boot: 196 boots: 6 failed, 182 passed with 8 untried/unknown (v5.5-rc6-450-ge24e77e03983)
Date: Thu, 16 Jan 2020 23:18:25 -0800 (PST) [thread overview]
Message-ID: <5e215fc1.1c69fb81.eb2b1.8255@mx.google.com> (raw)
next/pending-fixes boot: 196 boots: 6 failed, 182 passed with 8 untried/unknown (v5.5-rc6-450-ge24e77e03983)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/pending-fixes/kernel/v5.5-rc6-450-ge24e77e03983/
Full Build Summary: https://kernelci.org/build/next/branch/pending-fixes/kernel/v5.5-rc6-450-ge24e77e03983/
Tree: next
Branch: pending-fixes
Git Describe: v5.5-rc6-450-ge24e77e03983
Git Commit: e24e77e0398319862489009664e26837dd31e851
Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 69 unique boards, 17 SoC families, 25 builds out of 213
Boot Regressions Detected:
arm:
multi_v7_defconfig:
gcc-8:
am335x-boneblack:
lab-baylibre: new failure (last pass: v5.5-rc6-391-ga06ab7cd4c3b)
arm64:
defconfig:
gcc-8:
apq8096-db820c:
lab-bjorn: new failure (last pass: v5.5-rc6-391-ga06ab7cd4c3b)
meson-g12b-odroid-n2:
lab-baylibre: new failure (last pass: v5.5-rc6-391-ga06ab7cd4c3b)
meson-sm1-sei610:
lab-baylibre: new failure (last pass: v5.5-rc6-391-ga06ab7cd4c3b)
defconfig+CONFIG_RANDOMIZE_BASE=y:
gcc-8:
meson-gxl-s905x-libretech-cc:
lab-baylibre: new failure (last pass: v5.5-rc6-391-ga06ab7cd4c3b)
Boot Failures Detected:
arm64:
defconfig+CONFIG_RANDOMIZE_BASE=y:
gcc-8:
meson-gxl-s905x-libretech-cc: 1 failed lab
defconfig:
gcc-8:
apq8096-db820c: 1 failed lab
meson-sm1-sei610: 1 failed lab
msm8998-mtp: 1 failed lab
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8:
meson-gxbb-p200: 1 failed lab
arm:
exynos_defconfig:
gcc-8:
exynos5422-odroidxu3: 1 failed lab
---
For more info write to <info@kernelci.org>
reply other threads:[~2020-01-17 7:18 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=5e215fc1.1c69fb81.eb2b1.8255@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.