From: "kernelci.org bot" <bot@kernelci•org>
To: linux-next@vger•kernel.org
Subject: next/pending-fixes boot: 93 boots: 6 failed, 86 passed with 1 untried/unknown (v5.5-8929-g9e4730e1c5e0)
Date: Tue, 04 Feb 2020 03:38:13 -0800 (PST) [thread overview]
Message-ID: <5e3957a5.1c69fb81.e5132.8ad7@mx.google.com> (raw)
next/pending-fixes boot: 93 boots: 6 failed, 86 passed with 1 untried/unknown (v5.5-8929-g9e4730e1c5e0)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/pending-fixes/kernel/v5.5-8929-g9e4730e1c5e0/
Full Build Summary: https://kernelci.org/build/next/branch/pending-fixes/kernel/v5.5-8929-g9e4730e1c5e0/
Tree: next
Branch: pending-fixes
Git Describe: v5.5-8929-g9e4730e1c5e0
Git Commit: 9e4730e1c5e01cdb3f6cd218f77a521a67bdf7a6
Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 71 unique boards, 19 SoC families, 16 builds out of 183
Boot Regressions Detected:
arm:
multi_v7_defconfig+CONFIG_SMP=n:
gcc-8:
am335x-boneblack:
lab-drue: new failure (last pass: v5.5-8839-g56c8845edd39)
exynos4412-odroidx2:
lab-collabora: failing since 6 days (last pass: v5.5-rc7-366-g2e30f8d48084 - first fail: v5.5-3974-gf60232fa162d)
arm64:
defconfig:
gcc-8:
apq8096-db820c:
lab-bjorn: failing since 6 days (last pass: v5.5-rc7-366-g2e30f8d48084 - first fail: v5.5-3974-gf60232fa162d)
meson-g12b-a311d-khadas-vim3:
lab-baylibre: new failure (last pass: v5.5-8839-g56c8845edd39)
Boot Failures Detected:
arm:
sama5_defconfig:
gcc-8:
at91-sama5d4_xplained: 1 failed lab
multi_v7_defconfig+CONFIG_SMP=n:
gcc-8:
exynos4412-odroidx2: 1 failed lab
exynos5422-odroidxu3: 1 failed lab
arm64:
defconfig:
gcc-8:
apq8096-db820c: 1 failed lab
meson-g12b-a311d-khadas-vim3: 1 failed lab
msm8998-mtp: 1 failed lab
---
For more info write to <info@kernelci•org>
reply other threads:[~2020-02-04 11:38 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=5e3957a5.1c69fb81.e5132.8ad7@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