From: "kernelci.org bot" <bot@kernelci.org>
To: linux-next@vger.kernel.org
Subject: next/pending-fixes boot: 229 boots: 16 failed, 204 passed with 7 offline, 2 untried/unknown (v5.4-rc4-405-g61e08e6b0f15)
Date: Thu, 24 Oct 2019 21:50:11 -0700 (PDT) [thread overview]
Message-ID: <5db27f03.1c69fb81.21c85.a5b6@mx.google.com> (raw)
next/pending-fixes boot: 229 boots: 16 failed, 204 passed with 7 offline, 2 untried/unknown (v5.4-rc4-405-g61e08e6b0f15)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/pending-fixes/kernel/v5.4-rc4-405-g61e08e6b0f15/
Full Build Summary: https://kernelci.org/build/next/branch/pending-fixes/kernel/v5.4-rc4-405-g61e08e6b0f15/
Tree: next
Branch: pending-fixes
Git Describe: v5.4-rc4-405-g61e08e6b0f15
Git Commit: 61e08e6b0f15d065b132e9f2fb19bf00ccffa522
Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 84 unique boards, 25 SoC families, 28 builds out of 215
Boot Failures Detected:
arm:
multi_v7_defconfig+kselftest:
gcc-8:
bcm2836-rpi-2-b: 1 failed lab
meson8b-odroidc1: 1 failed lab
rk3288-rock2-square: 1 failed lab
multi_v7_defconfig+CONFIG_SMP=n:
gcc-8:
tegra124-jetson-tk1: 2 failed labs
multi_v7_defconfig+CONFIG_EFI=y+CONFIG_ARM_LPAE=y:
gcc-8:
tegra124-jetson-tk1: 2 failed labs
tegra_defconfig:
gcc-8:
tegra124-jetson-tk1: 2 failed labs
multi_v7_defconfig:
gcc-8:
tegra124-jetson-tk1: 2 failed labs
arm64:
defconfig+kselftest:
gcc-8:
r8a7796-m3ulcb: 2 failed labs
rk3399-puma-haikou: 1 failed lab
sun50i-h6-pine-h64: 1 failed lab
defconfig:
gcc-8:
apq8096-db820c: 1 failed lab
Offline Platforms:
arm:
qcom_defconfig:
gcc-8
qcom-apq8064-cm-qs600: 1 offline lab
davinci_all_defconfig:
gcc-8
dm365evm,legacy: 1 offline lab
sunxi_defconfig:
gcc-8
sun5i-r8-chip: 1 offline lab
sun7i-a20-bananapi: 1 offline lab
multi_v7_defconfig:
gcc-8
qcom-apq8064-cm-qs600: 1 offline lab
sun5i-r8-chip: 1 offline lab
sun7i-a20-bananapi: 1 offline lab
---
For more info write to <info@kernelci.org>
reply other threads:[~2019-10-25 4:50 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=5db27f03.1c69fb81.21c85.a5b6@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.