From: "kernelci.org bot" <bot@kernelci.org>
To: linux-next@vger.kernel.org
Subject: next/pending-fixes boot: 289 boots: 6 failed, 266 passed with 7 offline, 6 untried/unknown, 4 conflicts (v5.7-rc3-247-gf693cee801ec)
Date: Thu, 30 Apr 2020 08:02:16 -0700 (PDT) [thread overview]
Message-ID: <5eaae878.1c69fb81.85f2b.0720@mx.google.com> (raw)
next/pending-fixes boot: 289 boots: 6 failed, 266 passed with 7 offline, 6 untried/unknown, 4 conflicts (v5.7-rc3-247-gf693cee801ec)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/pending-fixes/kernel/v5.7-rc3-247-gf693cee801ec/
Full Build Summary: https://kernelci.org/build/next/branch/pending-fixes/kernel/v5.7-rc3-247-gf693cee801ec/
Tree: next
Branch: pending-fixes
Git Describe: v5.7-rc3-247-gf693cee801ec
Git Commit: f693cee801ecec79722128a2bf506d381df9ed9d
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 109 unique boards, 25 SoC families, 31 builds out of 217
Boot Regressions Detected:
arm:
exynos_defconfig:
gcc-8:
exynos5422-odroidxu3:
lab-collabora: failing since 1 day (last pass: v5.7-rc3-194-g1631e20d9729 - first fail: v5.7-rc3-228-g76a37a4cf830)
multi_v7_defconfig:
gcc-8:
bcm2836-rpi-2-b:
lab-collabora: failing since 76 days (last pass: v5.5-8839-g56c8845edd39 - first fail: v5.6-rc1-311-ge58961fba99f)
sun8i-h2-plus-orangepi-r1:
lab-baylibre: new failure (last pass: v5.7-rc3-228-g76a37a4cf830)
arm64:
defconfig:
gcc-8:
apq8096-db820c:
lab-bjorn: failing since 1 day (last pass: v5.7-rc3-194-g1631e20d9729 - first fail: v5.7-rc3-228-g76a37a4cf830)
meson-axg-s400:
lab-baylibre-seattle: new failure (last pass: v5.7-rc3-228-g76a37a4cf830)
meson-g12b-a311d-khadas-vim3:
lab-baylibre: new failure (last pass: v5.7-rc3-228-g76a37a4cf830)
meson-gxm-q200:
lab-baylibre: new failure (last pass: v5.7-rc3-228-g76a37a4cf830)
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8:
meson-axg-s400:
lab-baylibre-seattle: new failure (last pass: v5.7-rc3-228-g76a37a4cf830)
meson-gxl-s905d-p230:
lab-baylibre: new failure (last pass: v5.7-rc3-228-g76a37a4cf830)
defconfig+CONFIG_RANDOMIZE_BASE=y:
gcc-8:
meson-axg-s400:
lab-baylibre-seattle: new failure (last pass: v5.7-rc3-228-g76a37a4cf830)
i386:
i386_defconfig+kselftest:
gcc-8:
qemu_i386:
lab-collabora: new failure (last pass: v5.7-rc3-228-g76a37a4cf830)
riscv:
defconfig:
gcc-8:
sifive_fu540:
lab-baylibre-seattle: failing since 20 days (last pass: v5.6-12182-g8614d419a4d6 - first fail: v5.6-12503-g3a0f8793ae13)
x86_64:
x86_64_defconfig:
gcc-8:
qemu_x86_64:
lab-collabora: new failure (last pass: v5.7-rc3-228-g76a37a4cf830)
x86_64_defconfig+kvm_guest:
gcc-8:
qemu_x86_64:
lab-collabora: new failure (last pass: v5.7-rc3-228-g76a37a4cf830)
Boot Failures Detected:
riscv:
defconfig:
gcc-8:
sifive_fu540: 1 failed lab
arm64:
defconfig:
gcc-8:
apq8096-db820c: 1 failed lab
meson-gxm-q200: 1 failed lab
arm:
sama5_defconfig:
gcc-8:
at91-sama5d4_xplained: 1 failed lab
multi_v7_defconfig:
gcc-8:
bcm2836-rpi-2-b: 1 failed lab
exynos_defconfig:
gcc-8:
exynos5422-odroidxu3: 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
exynos5800-peach-pi: 1 offline lab
qcom-apq8064-cm-qs600: 1 offline lab
stih410-b2120: 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:
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-04-30 15:02 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=5eaae878.1c69fb81.85f2b.0720@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.