From: "kernelci.org bot" <bot@kernelci.org>
To: linux-next@vger.kernel.org
Subject: next/master boot: 252 boots: 12 failed, 239 passed with 1 untried/unknown (next-20190716)
Date: Tue, 16 Jul 2019 05:24:40 -0700 (PDT) [thread overview]
Message-ID: <5d2dc208.1c69fb81.8b2b9.e9d5@mx.google.com> (raw)
next/master boot: 252 boots: 12 failed, 239 passed with 1 untried/unknown (next-20190716)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20190716/
Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20190716/
Tree: next
Branch: master
Git Describe: next-20190716
Git Commit: 1438cde7c87cb5d59c4caa292f3d32e4ee06b763
Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 85 unique boards, 27 SoC families, 22 builds out of 230
Boot Failures Detected:
arm:
oxnas_v6_defconfig:
gcc-8:
ox820-cloudengines-pogoplug-series-3: 1 failed lab
sunxi_defconfig:
gcc-8:
sun7i-a20-bananapi: 1 failed lab
qcom_defconfig:
gcc-8:
qcom-apq8064-cm-qs600: 1 failed lab
qcom-apq8064-ifc6410: 1 failed lab
multi_v7_defconfig+CONFIG_EFI=y+CONFIG_ARM_LPAE=y:
gcc-8:
exynos4412-odroidx2: 1 failed lab
multi_v7_defconfig:
gcc-8:
sun7i-a20-bananapi: 1 failed lab
multi_v7_defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8:
armada-xp-openblocks-ax3-4: 1 failed lab
arm64:
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
clang-8:
meson-gxbb-nanopi-k2: 1 failed lab
meson-gxl-s905x-khadas-vim: 1 failed lab
defconfig:
gcc-8:
apq8096-db820c: 1 failed lab
defconfig+CONFIG_RANDOMIZE_BASE=y:
gcc-8:
meson-gxl-s905x-nexbox-a95x: 1 failed lab
meson-gxm-nexbox-a1: 1 failed lab
---
For more info write to <info@kernelci.org>
reply other threads:[~2019-07-16 12:24 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=5d2dc208.1c69fb81.8b2b9.e9d5@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.