From: "kernelci.org bot" <bot@kernelci.org>
To: linux-next@vger.kernel.org
Subject: next/master boot: 128 boots: 8 failed, 113 passed with 7 offline (next-20191022)
Date: Tue, 22 Oct 2019 04:34:14 -0700 (PDT) [thread overview]
Message-ID: <5daee936.1c69fb81.e8e17.a8a0@mx.google.com> (raw)
next/master boot: 128 boots: 8 failed, 113 passed with 7 offline (next-20191022)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20191022/
Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20191022/
Tree: next
Branch: master
Git Describe: next-20191022
Git Commit: a722f75b2923b4fd44c17e7255e822ac48fe85f0
Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 55 unique boards, 20 SoC families, 20 builds out of 219
Boot Failures Detected:
arm64:
defconfig:
gcc-8:
apq8096-db820c: 1 failed lab
defconfig+kselftest:
gcc-8:
rk3399-puma-haikou: 1 failed lab
arm:
multi_v7_defconfig+kselftest:
gcc-8:
bcm2836-rpi-2-b: 1 failed lab
rk3288-rock2-square: 1 failed lab
multi_v7_defconfig:
gcc-8:
tegra124-jetson-tk1: 1 failed lab
multi_v7_defconfig+CONFIG_EFI=y+CONFIG_ARM_LPAE=y:
gcc-8:
tegra124-jetson-tk1: 1 failed lab
tegra_defconfig:
gcc-8:
tegra124-jetson-tk1: 1 failed lab
multi_v7_defconfig+CONFIG_SMP=n:
gcc-8:
tegra124-jetson-tk1: 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
sun7i-a20-bananapi: 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-22 11:34 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=5daee936.1c69fb81.e8e17.a8a0@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.