From: "kernelci.org bot" <bot@kernelci.org>
To: linux-next@vger.kernel.org
Subject: next/pending-fixes boot: 281 boots: 9 failed, 262 passed with 6 offline, 4 untried/unknown (v5.4-rc3-311-gce15fc3fc1ae)
Date: Tue, 15 Oct 2019 20:59:40 -0700 (PDT) [thread overview]
Message-ID: <5da695ac.1c69fb81.75441.48c7@mx.google.com> (raw)
next/pending-fixes boot: 281 boots: 9 failed, 262 passed with 6 offline, 4 untried/unknown (v5.4-rc3-311-gce15fc3fc1ae)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/pending-fixes/kernel/v5.4-rc3-311-gce15fc3fc1ae/
Full Build Summary: https://kernelci.org/build/next/branch/pending-fixes/kernel/v5.4-rc3-311-gce15fc3fc1ae/
Tree: next
Branch: pending-fixes
Git Describe: v5.4-rc3-311-gce15fc3fc1ae
Git Commit: ce15fc3fc1ae8839fd1406206584a9f0697cd36d
Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 95 unique boards, 25 SoC families, 28 builds out of 215
Boot Failures Detected:
arm64:
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8:
meson-g12b-s922x-khadas-vim3: 1 failed lab
defconfig+kselftest:
gcc-8:
meson-gxm-khadas-vim2: 1 failed lab
r8a7796-m3ulcb: 2 failed labs
rk3399-puma-haikou: 1 failed lab
sun50i-h5-libretech-all-h3-cc: 1 failed lab
arm:
exynos_defconfig:
gcc-8:
exynos5422-odroidxu3: 1 failed lab
multi_v7_defconfig+kselftest:
gcc-8:
bcm2836-rpi-2-b: 1 failed lab
rk3288-rock2-square: 1 failed lab
Offline Platforms:
arm:
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
davinci_all_defconfig:
gcc-8
dm365evm,legacy: 1 offline lab
qcom_defconfig:
gcc-8
qcom-apq8064-cm-qs600: 1 offline lab
---
For more info write to <info@kernelci.org>
reply other threads:[~2019-10-16 3:59 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=5da695ac.1c69fb81.75441.48c7@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).