From: "kernelci.org bot" <bot@kernelci•org>
To: linux-next@vger•kernel.org
Subject: next/master boot: 97 boots: 4 failed, 90 passed with 2 offline, 1 untried/unknown (next-20200312)
Date: Thu, 12 Mar 2020 09:18:00 -0700 (PDT) [thread overview]
Message-ID: <5e6a60b8.1c69fb81.234e5.44af@mx.google.com> (raw)
next/master boot: 97 boots: 4 failed, 90 passed with 2 offline, 1 untried/unknown (next-20200312)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20200312/
Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20200312/
Tree: next
Branch: master
Git Describe: next-20200312
Git Commit: 407b0a62b422526e943e1261c7939b2e52ee17cb
Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 59 unique boards, 19 SoC families, 24 builds out of 329
Boot Regressions Detected:
arm:
multi_v7_defconfig+CONFIG_EFI=y+CONFIG_ARM_LPAE=y:
gcc-8:
exynos5422-odroidxu3:
lab-collabora: new failure (last pass: next-20200306)
sama5_defconfig:
gcc-8:
at91-sama5d4_xplained:
lab-baylibre: failing since 23 days (last pass: next-20200214 - first fail: next-20200217)
versatile_defconfig:
gcc-8:
versatile-pb:
lab-collabora: new failure (last pass: next-20200311)
Boot Failures Detected:
arm:
multi_v7_defconfig:
gcc-8:
exynos5800-peach-pi: 1 failed lab
multi_v7_defconfig+CONFIG_EFI=y+CONFIG_ARM_LPAE=y:
gcc-8:
exynos5422-odroidxu3: 1 failed lab
exynos_defconfig:
gcc-8:
exynos5800-peach-pi: 1 failed lab
sama5_defconfig:
gcc-8:
at91-sama5d4_xplained: 1 failed lab
Offline Platforms:
arm:
multi_v7_defconfig:
gcc-8
qcom-apq8064-cm-qs600: 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:[~2020-03-12 16:18 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=5e6a60b8.1c69fb81.234e5.44af@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