From: "kernelci.org bot" <bot@kernelci.org>
To: linux-next@vger.kernel.org
Subject: next/pending-fixes boot: 276 boots: 4 failed, 264 passed with 6 offline, 1 untried/unknown, 1 conflict (v5.4-13395-gf8186a61dbcf)
Date: Sat, 07 Dec 2019 20:23:26 -0800 (PST) [thread overview]
Message-ID: <5dec7abe.1c69fb81.c42a5.213e@mx.google.com> (raw)
next/pending-fixes boot: 276 boots: 4 failed, 264 passed with 6 offline, 1 untried/unknown, 1 conflict (v5.4-13395-gf8186a61dbcf)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/pending-fixes/kernel/v5.4-13395-gf8186a61dbcf/
Full Build Summary: https://kernelci.org/build/next/branch/pending-fixes/kernel/v5.4-13395-gf8186a61dbcf/
Tree: next
Branch: pending-fixes
Git Describe: v5.4-13395-gf8186a61dbcf
Git Commit: f8186a61dbcfd6a618097dfba5311323b27addc9
Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 97 unique boards, 26 SoC families, 30 builds out of 214
Boot Failures Detected:
arm:
qcom_defconfig:
gcc-8:
qcom-apq8064-cm-qs600: 1 failed lab
arm64:
defconfig:
gcc-8:
meson-g12b-odroid-n2: 1 failed lab
rk3399-gru-kevin: 1 failed lab
defconfig+CONFIG_RANDOMIZE_BASE=y:
gcc-8:
juno-r2: 1 failed lab
Offline Platforms:
arm:
exynos_defconfig:
gcc-8
exynos5800-peach-pi: 1 offline lab
davinci_all_defconfig:
gcc-8
dm365evm,legacy: 1 offline lab
sunxi_defconfig:
gcc-8
sun7i-a20-bananapi: 1 offline lab
multi_v7_defconfig:
gcc-8
exynos5800-peach-pi: 1 offline lab
mt7623n-bananapi-bpi-r2: 1 offline lab
sun7i-a20-bananapi: 1 offline lab
Conflicting Boot Failure Detected: (These likely are not failures as other labs are reporting PASS. Needs review.)
arm:
multi_v7_defconfig:
imx6q-sabrelite:
lab-baylibre: PASS (gcc-8)
lab-collabora: FAIL (gcc-8)
---
For more info write to <info@kernelci.org>
reply other threads:[~2019-12-08 4:23 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=5dec7abe.1c69fb81.c42a5.213e@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).