From: "kernelci.org bot" <bot@kernelci•org>
To: linux-next@vger•kernel.org
Subject: next/master boot: 194 boots: 8 failed, 185 passed with 1 conflict (next-20190708)
Date: Mon, 08 Jul 2019 14:03:27 -0700 (PDT) [thread overview]
Message-ID: <5d23af9f.1c69fb81.545c2.b0df@mx.google.com> (raw)
next/master boot: 194 boots: 8 failed, 185 passed with 1 conflict (next-20190708)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20190708/
Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20190708/
Tree: next
Branch: master
Git Describe: next-20190708
Git Commit: d58b5ab90ee7528126fd5833df7fc5bda8331ce8
Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 73 unique boards, 25 SoC families, 20 builds out of 228
Boot Regressions Detected:
arm:
multi_v7_defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8:
armada-xp-openblocks-ax3-4:
lab-baylibre-seattle: failing since 13 days (last pass: next-20190624 - first fail: next-20190625)
qcom_defconfig:
gcc-8:
qcom-apq8064-cm-qs600:
lab-baylibre-seattle: failing since 17 days (last pass: next-20190619 - first fail: next-20190621)
qcom-apq8064-ifc6410:
lab-baylibre-seattle: failing since 17 days (last pass: next-20190618 - first fail: next-20190620)
Boot Failures Detected:
arm:
multi_v7_defconfig+CONFIG_EFI=y+CONFIG_ARM_LPAE=y:
gcc-8:
exynos4412-odroidx2: 1 failed lab
multi_v7_defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8:
armada-xp-openblocks-ax3-4: 1 failed lab
sunxi_defconfig:
gcc-8:
sun7i-a20-bananapi: 1 failed lab
multi_v7_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
arm64:
defconfig:
gcc-8:
rk3399-firefly: 1 failed lab
Conflicting Boot Failure Detected: (These likely are not failures as other labs are reporting PASS. Needs review.)
arm:
multi_v7_defconfig+CONFIG_SMP=n:
am57xx-beagle-x15:
lab-drue: PASS (gcc-8)
lab-linaro-lkft: FAIL (gcc-8)
---
For more info write to <info@kernelci•org>
reply other threads:[~2019-07-08 21:03 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=5d23af9f.1c69fb81.545c2.b0df@mx.google.com \
--to=bot@kernelci$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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