From: "kernelci.org bot" <bot@kernelci.org>
To: linux-next@vger.kernel.org
Subject: next/master boot: 218 boots: 8 failed, 196 passed with 13 offline, 1 conflict (next-20190830)
Date: Fri, 30 Aug 2019 16:57:43 -0700 (PDT) [thread overview]
Message-ID: <5d69b7f7.1c69fb81.659a3.66d4@mx.google.com> (raw)
next/master boot: 218 boots: 8 failed, 196 passed with 13 offline, 1 conflict (next-20190830)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20190830/
Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20190830/
Tree: next
Branch: master
Git Describe: next-20190830
Git Commit: 6d028043b55e54f48fbdf62ea8ce11a4ad830cac
Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 93 unique boards, 28 SoC families, 19 builds out of 217
Boot Failures Detected:
arm64:
defconfig:
gcc-8:
apq8096-db820c: 1 failed lab
mt7622-rfb1: 1 failed lab
defconfig+CONFIG_RANDOMIZE_BASE=y:
gcc-8:
mt7622-rfb1: 1 failed lab
arm:
vexpress_defconfig:
gcc-8:
qemu_arm-virt-gicv3: 5 failed labs
Offline Platforms:
mips:
pistachio_defconfig:
gcc-8
pistachio_marduk: 1 offline lab
arm64:
defconfig:
gcc-8
apq8016-sbc: 1 offline lab
meson-gxbb-odroidc2: 1 offline lab
defconfig+CONFIG_RANDOMIZE_BASE=y:
gcc-8
apq8016-sbc: 1 offline lab
meson-gxbb-odroidc2: 1 offline lab
meson-gxl-s905x-nexbox-a95x: 1 offline lab
arm:
multi_v7_defconfig:
gcc-8
qcom-apq8064-cm-qs600: 1 offline lab
qcom-apq8064-ifc6410: 1 offline lab
sun5i-r8-chip: 1 offline lab
qcom_defconfig:
gcc-8
qcom-apq8064-cm-qs600: 1 offline lab
qcom-apq8064-ifc6410: 1 offline lab
sunxi_defconfig:
gcc-8
sun5i-r8-chip: 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:
tegra_defconfig:
tegra124-jetson-tk1:
lab-baylibre: FAIL (gcc-8)
lab-mhart: PASS (gcc-8)
lab-collabora: PASS (gcc-8)
---
For more info write to <info@kernelci.org>
reply other threads:[~2019-08-30 23:57 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=5d69b7f7.1c69fb81.659a3.66d4@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).