From: "kernelci.org bot" <bot@kernelci.org>
To: linux-next@vger.kernel.org
Subject: next/master boot: 114 boots: 16 failed, 95 passed with 3 untried/unknown (next-20200114)
Date: Tue, 14 Jan 2020 03:24:07 -0800 (PST) [thread overview]
Message-ID: <5e1da4d7.1c69fb81.8716f.baed@mx.google.com> (raw)
next/master boot: 114 boots: 16 failed, 95 passed with 3 untried/unknown (next-20200114)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20200114/
Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20200114/
Tree: next
Branch: master
Git Describe: next-20200114
Git Commit: 1b851f985f514a7a173e5c55b9fdbf5d18f9ea74
Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 49 unique boards, 11 SoC families, 22 builds out of 215
Boot Regressions Detected:
arm:
multi_v7_defconfig:
gcc-8:
omap4-panda:
lab-baylibre: failing since 8 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)
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)
meson-g12b-a311d-khadas-vim3:
lab-baylibre: new failure (last pass: next-20200113)
meson-gxl-s905x-khadas-vim:
lab-baylibre: new failure (last pass: next-20200113)
sun50i-a64-pine64-plus:
lab-baylibre: new failure (last pass: next-20200113)
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8:
meson-gxl-s805x-libretech-ac:
lab-baylibre: new failure (last pass: next-20200113)
meson-gxl-s805x-p241:
lab-baylibre: failing since 1 day (last pass: next-20200110 - first fail: next-20200113)
sun50i-a64-pine64-plus:
lab-baylibre: failing since 1 day (last pass: next-20200110 - first fail: next-20200113)
defconfig+CONFIG_RANDOMIZE_BASE=y:
gcc-8:
sun50i-a64-pine64-plus:
lab-baylibre: failing since 1 day (last pass: next-20200110 - first fail: next-20200113)
i386:
i386_defconfig:
gcc-8:
qemu_i386:
lab-baylibre: new failure (last pass: next-20200113)
Boot Failures Detected:
arm64:
defconfig:
gcc-8:
apq8016-sbc: 1 failed lab
meson-g12b-a311d-khadas-vim3: 1 failed lab
meson-gxl-s905x-khadas-vim: 1 failed lab
msm8998-mtp: 1 failed lab
sun50i-a64-pine64-plus: 1 failed lab
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8:
meson-gxl-s805x-libretech-ac: 1 failed lab
sun50i-a64-pine64-plus: 1 failed lab
i386:
i386_defconfig:
gcc-8:
qemu_i386: 1 failed lab
arm:
omap2plus_defconfig:
gcc-8:
am335x-boneblack: 1 failed lab
omap4-panda: 1 failed lab
multi_v7_defconfig:
gcc-8:
am335x-boneblack: 1 failed lab
meson8b-odroidc1: 1 failed lab
omap4-panda: 1 failed lab
multi_v7_defconfig+CONFIG_SMP=n:
gcc-8:
am335x-boneblack: 1 failed lab
meson8b-odroidc1: 1 failed lab
omap4-panda: 1 failed lab
---
For more info write to <info@kernelci.org>
reply other threads:[~2020-01-14 11: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=5e1da4d7.1c69fb81.8716f.baed@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.