From: "kernelci.org bot" <bot@kernelci.org>
To: linux-next@vger.kernel.org
Subject: next/master boot: 184 boots: 14 failed, 166 passed with 4 untried/unknown (next-20200113)
Date: Mon, 13 Jan 2020 06:17:31 -0800 (PST) [thread overview]
Message-ID: <5e1c7bfb.1c69fb81.3cd71.b956@mx.google.com> (raw)
next/master boot: 184 boots: 14 failed, 166 passed with 4 untried/unknown (next-20200113)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20200113/
Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20200113/
Tree: next
Branch: master
Git Describe: next-20200113
Git Commit: 8a28e614e1dba64463521149af18a2fede7d9e08
Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 64 unique boards, 16 SoC families, 25 builds out of 215
Boot Regressions Detected:
arm:
exynos_defconfig:
gcc-8:
exynos5422-odroidxu3:
lab-collabora: new failure (last pass: next-20200110)
multi_v7_defconfig:
gcc-8:
omap4-panda:
lab-baylibre: failing since 7 days (last pass: next-20191220 - first fail: next-20200106)
multi_v7_defconfig+CONFIG_SMP=n:
gcc-8:
omap4-panda:
lab-baylibre: failing since 7 days (last pass: next-20191220 - first fail: next-20200106)
sun8i-a83t-bananapi-m3:
lab-clabbe: new failure (last pass: next-20200110)
omap2plus_defconfig:
gcc-8:
omap4-panda:
lab-baylibre: failing since 7 days (last pass: next-20191220 - first fail: next-20200106)
arm64:
defconfig:
gcc-8:
apq8016-sbc:
lab-bjorn: failing since 7 days (last pass: next-20191220 - first fail: next-20200106)
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8:
meson-gxl-s805x-p241:
lab-baylibre: new failure (last pass: next-20200110)
meson-gxm-q200:
lab-baylibre: new failure (last pass: next-20200110)
sun50i-a64-pine64-plus:
lab-baylibre: new failure (last pass: next-20200110)
defconfig+CONFIG_RANDOMIZE_BASE=y:
gcc-8:
sun50i-a64-pine64-plus:
lab-baylibre: new failure (last pass: next-20200110)
Boot Failures Detected:
arm64:
defconfig:
gcc-8:
apq8016-sbc: 1 failed lab
msm8998-mtp: 1 failed lab
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8:
meson-gxl-s805x-p241: 1 failed lab
meson-gxm-q200: 1 failed lab
sun50i-a64-pine64-plus: 1 failed lab
arm:
omap2plus_defconfig:
gcc-8:
omap4-panda: 2 failed labs
exynos_defconfig:
gcc-8:
exynos5422-odroidxu3: 1 failed lab
multi_v7_defconfig:
gcc-8:
meson8b-odroidc1: 1 failed lab
omap4-panda: 2 failed labs
multi_v7_defconfig+CONFIG_SMP=n:
gcc-8:
meson8b-odroidc1: 1 failed lab
omap4-panda: 2 failed labs
---
For more info write to <info@kernelci.org>
reply other threads:[~2020-01-13 14:17 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=5e1c7bfb.1c69fb81.3cd71.b956@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).