From: "kernelci.org bot" <bot@kernelci.org>
To: linux-next@vger.kernel.org
Subject: next/master boot: 293 boots: 10 failed, 268 passed with 4 offline, 7 untried/unknown, 4 conflicts (next-20200424)
Date: Fri, 24 Apr 2020 21:31:54 -0700 (PDT) [thread overview]
Message-ID: <5ea3bd3a.1c69fb81.3a9d2.2fd1@mx.google.com> (raw)
next/master boot: 293 boots: 10 failed, 268 passed with 4 offline, 7 untried/unknown, 4 conflicts (next-20200424)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20200424/
Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20200424/
Tree: next
Branch: master
Git Describe: next-20200424
Git Commit: 8bdabd09ec86a993419c8c98a4f34c12bc902c6c
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 111 unique boards, 26 SoC families, 31 builds out of 231
Boot Regressions Detected:
arc:
hsdk_defconfig:
gcc-8:
hsdk:
lab-baylibre: new failure (last pass: next-20200417)
arm:
sama5_defconfig:
gcc-8:
at91-sama5d4_xplained:
lab-baylibre: failing since 67 days (last pass: next-20200214 - first fail: next-20200217)
arm64:
defconfig:
gcc-8:
meson-axg-s400:
lab-baylibre-seattle: new failure (last pass: next-20200423)
meson-gxl-s805x-libretech-ac:
lab-baylibre: new failure (last pass: next-20200417)
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8:
meson-axg-s400:
lab-baylibre-seattle: new failure (last pass: next-20200423)
meson-gxm-q200:
lab-baylibre: new failure (last pass: next-20200417)
sun50i-a64-pine64-plus:
lab-baylibre: new failure (last pass: next-20200417)
defconfig+CONFIG_RANDOMIZE_BASE=y:
gcc-8:
meson-axg-s400:
lab-baylibre-seattle: new failure (last pass: next-20200423)
sun50i-a64-pine64-plus:
lab-baylibre: new failure (last pass: next-20200417)
i386:
i386_defconfig:
gcc-8:
qemu_i386:
lab-collabora: new failure (last pass: next-20200423)
i386_defconfig+kselftest:
gcc-8:
qemu_i386:
lab-collabora: new failure (last pass: next-20200423)
riscv:
defconfig:
gcc-8:
sifive_fu540:
lab-baylibre-seattle: failing since 28 days (last pass: next-20200326 - first fail: next-20200327)
x86_64:
x86_64_defconfig:
gcc-8:
qemu_x86_64:
lab-baylibre: new failure (last pass: next-20200423)
lab-collabora: new failure (last pass: next-20200423)
Boot Failures Detected:
riscv:
defconfig:
gcc-8:
sifive_fu540: 1 failed lab
arm64:
defconfig:
gcc-8:
meson-gxl-s805x-libretech-ac: 1 failed lab
defconfig+CONFIG_RANDOMIZE_BASE=y:
gcc-8:
sun50i-a64-pine64-plus: 1 failed lab
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8:
meson-gxm-q200: 1 failed lab
sun50i-a64-pine64-plus: 1 failed lab
x86_64:
x86_64_defconfig:
gcc-8:
qemu_x86_64: 2 failed labs
arm:
sama5_defconfig:
gcc-8:
at91-sama5d4_xplained: 1 failed lab
multi_v7_defconfig:
gcc-8:
bcm2836-rpi-2-b: 1 failed lab
imx_v6_v7_defconfig:
gcc-8:
imx7s-warp: 1 failed lab
Offline Platforms:
arm64:
defconfig:
gcc-8
meson-axg-s400: 1 offline lab
defconfig+CONFIG_RANDOMIZE_BASE=y:
gcc-8
meson-axg-s400: 1 offline lab
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8
meson-axg-s400: 1 offline lab
arm:
multi_v7_defconfig:
gcc-8
qcom-apq8064-cm-qs600: 1 offline lab
Conflicting Boot Failures Detected: (These likely are not failures as other labs are reporting PASS. Needs review.)
i386:
i386_defconfig+kselftest:
qemu_i386:
lab-baylibre: PASS (gcc-8)
lab-collabora: FAIL (gcc-8)
i386_defconfig:
qemu_i386:
lab-baylibre: PASS (gcc-8)
lab-collabora: FAIL (gcc-8)
x86_64:
x86_64_defconfig+kselftest:
qemu_x86_64:
lab-baylibre: FAIL (gcc-8)
lab-collabora: PASS (gcc-8)
x86_64_defconfig+kvm_guest:
qemu_x86_64:
lab-baylibre: PASS (gcc-8)
lab-collabora: FAIL (gcc-8)
---
For more info write to <info@kernelci.org>
reply other threads:[~2020-04-25 4:31 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=5ea3bd3a.1c69fb81.3a9d2.2fd1@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).