From: "kernelci.org bot" <bot@kernelci•org>
To: linux-next@vger•kernel.org
Subject: next/master boot: 241 boots: 17 failed, 215 passed with 5 offline, 4 conflicts (next-20200507)
Date: Thu, 07 May 2020 07:52:23 -0700 (PDT) [thread overview]
Message-ID: <5eb420a7.1c69fb81.f9406.fa41@mx.google.com> (raw)
next/master boot: 241 boots: 17 failed, 215 passed with 5 offline, 4 conflicts (next-20200507)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20200507/
Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20200507/
Tree: next
Branch: master
Git Describe: next-20200507
Git Commit: 6b43f715b6379433e8eb30aa9bcc99bd6a585f77
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 94 unique boards, 22 SoC families, 23 builds out of 231
Boot Regressions Detected:
arm:
multi_v7_defconfig:
gcc-8:
tegra124-jetson-tk1:
lab-collabora: new failure (last pass: next-20200505)
tegra124-nyan-big:
lab-collabora: new failure (last pass: next-20200505)
multi_v7_defconfig+CONFIG_EFI=y+CONFIG_ARM_LPAE=y:
gcc-8:
tegra124-jetson-tk1:
lab-collabora: new failure (last pass: next-20200505)
tegra124-nyan-big:
lab-collabora: new failure (last pass: next-20200505)
multi_v7_defconfig+CONFIG_SMP=n:
gcc-8:
tegra124-jetson-tk1:
lab-collabora: new failure (last pass: next-20200505)
tegra124-nyan-big:
lab-collabora: new failure (last pass: next-20200505)
tegra_defconfig:
gcc-8:
tegra124-jetson-tk1:
lab-collabora: new failure (last pass: next-20200505)
tegra124-nyan-big:
lab-collabora: new failure (last pass: next-20200505)
tegra30-beaver:
lab-baylibre-seattle: new failure (last pass: next-20200505)
arm64:
defconfig:
clang-9:
apq8016-sbc:
lab-bjorn: new failure (last pass: next-20200505)
sm8150-mtp:
lab-bjorn: failing since 1 day (last pass: next-20200430 - first fail: next-20200505)
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8:
meson-gxm-khadas-vim2:
lab-baylibre: new failure (last pass: next-20200505)
i386:
i386_defconfig+kselftest:
gcc-8:
qemu_i386:
lab-collabora: new failure (last pass: next-20200505)
riscv:
defconfig:
gcc-8:
sifive_fu540:
lab-baylibre-seattle: failing since 40 days (last pass: next-20200326 - first fail: next-20200327)
Boot Failures Detected:
riscv:
defconfig:
gcc-8:
sifive_fu540: 1 failed lab
arm64:
defconfig:
gcc-8:
mt7622-rfb1: 1 failed lab
defconfig+CONFIG_RANDOMIZE_BASE=y:
gcc-8:
mt7622-rfb1: 1 failed lab
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8:
meson-gxm-khadas-vim2: 1 failed lab
arm:
tegra_defconfig:
gcc-8:
tegra124-jetson-tk1: 1 failed lab
tegra124-nyan-big: 1 failed lab
tegra30-beaver: 1 failed lab
multi_v7_defconfig:
gcc-8:
bcm2836-rpi-2-b: 1 failed lab
tegra124-jetson-tk1: 1 failed lab
tegra124-nyan-big: 1 failed lab
tegra30-beaver: 1 failed lab
multi_v7_defconfig+CONFIG_EFI=y+CONFIG_ARM_LPAE=y:
gcc-8:
tegra124-jetson-tk1: 1 failed lab
tegra124-nyan-big: 1 failed lab
multi_v7_defconfig+CONFIG_SMP=n:
gcc-8:
tegra124-jetson-tk1: 1 failed lab
tegra124-nyan-big: 1 failed lab
Offline Platforms:
arm:
multi_v7_defconfig:
gcc-8
exynos5800-peach-pi: 1 offline lab
qcom-apq8064-cm-qs600: 1 offline lab
stih410-b2120: 1 offline lab
qcom_defconfig:
gcc-8
qcom-apq8064-cm-qs600: 1 offline lab
exynos_defconfig:
gcc-8
exynos5800-peach-pi: 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: PASS (gcc-8)
lab-collabora: FAIL (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-05-07 14:52 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=5eb420a7.1c69fb81.f9406.fa41@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