From: "kernelci.org bot" <bot@kernelci.org>
To: linux-next@vger.kernel.org
Subject: next/master boot: 252 boots: 12 failed, 229 passed with 11 offline (next-20190621)
Date: Fri, 21 Jun 2019 09:56:25 -0700 (PDT) [thread overview]
Message-ID: <5d0d0c39.1c69fb81.f9db.77fc@mx.google.com> (raw)
next/master boot: 252 boots: 12 failed, 229 passed with 11 offline (next-20190621)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20190621/
Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20190621/
Tree: next
Branch: master
Git Describe: next-20190621
Git Commit: e2d28c40292bdc35553d599e5bbbeaefbab49416
Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 85 unique boards, 24 SoC families, 17 builds out of 230
Boot Regressions Detected:
arm:
qcom_defconfig:
gcc-8:
qcom-msm8974-sony-xperia-castor:
lab-bjorn: failing since 3 days (last pass: next-20190617 - first fail: next-20190618)
arm64:
defconfig:
gcc-8:
rk3399-firefly:
lab-baylibre-seattle: new failure (last pass: next-20190617)
Boot Failures Detected:
arm:
qcom_defconfig:
gcc-8:
qcom-msm8974-sony-xperia-castor: 1 failed lab
multi_v7_defconfig+CONFIG_EFI=y+CONFIG_ARM_LPAE=y:
gcc-8:
exynos4412-odroidx2: 1 failed lab
arm64:
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8:
meson-g12b-odroid-n2: 1 failed lab
defconfig:
gcc-8:
meson-g12b-odroid-n2: 1 failed lab
rk3399-firefly: 1 failed lab
defconfig+CONFIG_RANDOMIZE_BASE=y:
gcc-8:
meson-g12b-odroid-n2: 1 failed lab
Offline Platforms:
arm:
exynos_defconfig:
gcc-8
exynos5250-arndale: 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
multi_v7_defconfig:
gcc-8
exynos5250-arndale: 1 offline lab
qcom-apq8064-ifc6410: 1 offline lab
sun5i-r8-chip: 1 offline lab
sun7i-a20-bananapi: 1 offline lab
arm64:
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8
apq8016-sbc: 1 offline lab
defconfig:
gcc-8
apq8016-sbc: 1 offline lab
---
For more info write to <info@kernelci.org>
reply other threads:[~2019-06-21 16:56 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=5d0d0c39.1c69fb81.f9db.77fc@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).