From: "kernelci.org bot" <bot@kernelci.org>
To: linux-next@vger.kernel.org
Subject: next/master boot: 316 boots: 18 failed, 276 passed with 22 offline (next-20190919)
Date: Thu, 19 Sep 2019 15:11:32 -0700 (PDT) [thread overview]
Message-ID: <5d83fd14.1c69fb81.52bf.d2fe@mx.google.com> (raw)
next/master boot: 316 boots: 18 failed, 276 passed with 22 offline (next-20190919)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20190919/
Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20190919/
Tree: next
Branch: master
Git Describe: next-20190919
Git Commit: eb2f12732f67eea9914f1c37c1f10d27127063c6
Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 89 unique boards, 27 SoC families, 25 builds out of 218
Boot Failures Detected:
arm64:
defconfig:
gcc-8:
apq8096-db820c: 1 failed lab
rk3399-firefly: 1 failed lab
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8:
meson-g12b-s922x-khadas-vim3: 1 failed lab
defconfig+kselftest:
gcc-8:
qcom-qdf2400: 1 failed lab
r8a7795-salvator-x: 1 failed lab
r8a7796-m3ulcb: 2 failed labs
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
rk3288-veyron-jaq: 1 failed lab
multi_v7_defconfig:
gcc-8:
rk3288-rock2-square: 1 failed lab
rk3288-veyron-jaq: 1 failed lab
multi_v7_defconfig+CONFIG_EFI=y+CONFIG_ARM_LPAE=y:
gcc-8:
rk3288-rock2-square: 1 failed lab
rk3288-veyron-jaq: 1 failed lab
sunxi_defconfig:
gcc-8:
sun7i-a20-cubieboard2: 1 failed lab
multi_v7_defconfig+CONFIG_SMP=n:
gcc-8:
rk3288-rock2-square: 1 failed lab
rk3288-veyron-jaq: 1 failed lab
Offline Platforms:
arm64:
defconfig:
gcc-8
apq8016-sbc: 1 offline lab
juno-r2: 1 offline lab
mt7622-rfb1: 1 offline lab
defconfig+CONFIG_RANDOMIZE_BASE=y:
gcc-8
apq8016-sbc: 1 offline lab
juno-r2: 1 offline lab
mt7622-rfb1: 1 offline lab
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8
apq8016-sbc: 1 offline lab
juno-r2: 1 offline lab
arm:
sama5_defconfig:
gcc-8
at91-sama5d4ek: 1 offline lab
sunxi_defconfig:
gcc-8
sun5i-r8-chip: 1 offline lab
sun7i-a20-bananapi: 1 offline lab
bcm2835_defconfig:
gcc-8
bcm2835-rpi-b: 1 offline lab
multi_v7_defconfig:
gcc-8
alpine-db: 1 offline lab
at91-sama5d4ek: 1 offline lab
qcom-apq8064-cm-qs600: 1 offline lab
qcom-apq8064-ifc6410: 1 offline lab
socfpga_cyclone5_de0_sockit: 1 offline lab
sun5i-r8-chip: 1 offline lab
socfpga_defconfig:
gcc-8
socfpga_cyclone5_de0_sockit: 1 offline lab
davinci_all_defconfig:
gcc-8
dm365evm,legacy: 1 offline lab
qcom_defconfig:
gcc-8
qcom-apq8064-cm-qs600: 1 offline lab
qcom-apq8064-ifc6410: 1 offline lab
---
For more info write to <info@kernelci.org>
reply other threads:[~2019-09-19 22:11 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=5d83fd14.1c69fb81.52bf.d2fe@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.