From: "kernelci.org bot" <bot@kernelci.org>
To: linux-next@vger.kernel.org
Subject: next/master boot: 249 boots: 13 failed, 225 passed with 5 offline, 6 untried/unknown (next-20200511)
Date: Mon, 11 May 2020 13:36:57 -0700 (PDT) [thread overview]
Message-ID: <5eb9b769.1c69fb81.cd8a3.470e@mx.google.com> (raw)
next/master boot: 249 boots: 13 failed, 225 passed with 5 offline, 6 untried/unknown (next-20200511)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20200511/
Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20200511/
Tree: next
Branch: master
Git Describe: next-20200511
Git Commit: 4b20e7462caa697f8a2cdab04ed8a5881cc65427
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 104 unique boards, 24 SoC families, 29 builds out of 228
Boot Regressions Detected:
arm:
imx_v6_v7_defconfig:
gcc-8:
imx6dl-wandboard_dual:
lab-baylibre-seattle: new failure (last pass: next-20200508)
imx6dl-wandboard_solo:
lab-baylibre-seattle: new failure (last pass: next-20200508)
multi_v7_defconfig:
gcc-8:
tegra124-jetson-tk1:
lab-collabora: failing since 4 days (last pass: next-20200505 - first fail: next-20200507)
multi_v7_defconfig+CONFIG_EFI=y+CONFIG_ARM_LPAE=y:
gcc-8:
tegra124-jetson-tk1:
lab-collabora: failing since 4 days (last pass: next-20200505 - first fail: next-20200507)
multi_v7_defconfig+CONFIG_SMP=n:
gcc-8:
tegra124-jetson-tk1:
lab-collabora: failing since 4 days (last pass: next-20200505 - first fail: next-20200507)
sama5_defconfig:
gcc-8:
at91-sama5d4_xplained:
lab-baylibre: failing since 83 days (last pass: next-20200214 - first fail: next-20200217)
tegra_defconfig:
gcc-8:
tegra124-jetson-tk1:
lab-collabora: failing since 4 days (last pass: next-20200505 - first fail: next-20200507)
tegra30-beaver:
lab-baylibre-seattle: failing since 4 days (last pass: next-20200505 - first fail: next-20200507)
versatile_defconfig:
gcc-8:
versatile-pb:
lab-collabora: new failure (last pass: next-20200508)
arm64:
defconfig:
clang-9:
apq8016-sbc:
lab-bjorn: failing since 4 days (last pass: next-20200505 - first fail: next-20200507)
gcc-8:
sun50i-a64-pine64-plus:
lab-baylibre: new failure (last pass: next-20200508)
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8:
meson-gxl-s805x-libretech-ac:
lab-baylibre: new failure (last pass: next-20200508)
sun50i-a64-pine64-plus:
lab-baylibre: new failure (last pass: next-20200508)
riscv:
defconfig:
gcc-8:
sifive_fu540:
lab-baylibre-seattle: failing since 45 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
sun50i-a64-pine64-plus: 1 failed lab
defconfig+CONFIG_RANDOMIZE_BASE=y:
gcc-8:
mt7622-rfb1: 1 failed lab
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8:
meson-gxl-s805x-libretech-ac: 1 failed lab
arm:
sama5_defconfig:
gcc-8:
at91-sama5d4_xplained: 1 failed lab
tegra_defconfig:
gcc-8:
tegra124-jetson-tk1: 1 failed lab
tegra30-beaver: 1 failed lab
multi_v7_defconfig:
gcc-8:
tegra124-jetson-tk1: 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
multi_v7_defconfig+CONFIG_SMP=n:
gcc-8:
tegra124-jetson-tk1: 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
---
For more info write to <info@kernelci.org>
reply other threads:[~2020-05-11 20:37 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=5eb9b769.1c69fb81.cd8a3.470e@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.