From: "kernelci.org bot" <bot@kernelci.org>
To: linux-next@vger.kernel.org
Subject: next/pending-fixes boot: 265 boots: 7 failed, 248 passed with 8 offline, 2 untried/unknown (v5.5-rc7-366-g2e30f8d48084)
Date: Fri, 24 Jan 2020 12:13:39 -0800 (PST) [thread overview]
Message-ID: <5e2b4ff3.1c69fb81.22b9c.49bb@mx.google.com> (raw)
next/pending-fixes boot: 265 boots: 7 failed, 248 passed with 8 offline, 2 untried/unknown (v5.5-rc7-366-g2e30f8d48084)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/pending-fixes/kernel/v5.5-rc7-366-g2e30f8d48084/
Full Build Summary: https://kernelci.org/build/next/branch/pending-fixes/kernel/v5.5-rc7-366-g2e30f8d48084/
Tree: next
Branch: pending-fixes
Git Describe: v5.5-rc7-366-g2e30f8d48084
Git Commit: 2e30f8d480842313c3de748bedd0a469f131f12e
Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 102 unique boards, 26 SoC families, 29 builds out of 210
Boot Failures Detected:
arm64:
defconfig+CONFIG_RANDOMIZE_BASE=y:
gcc-8:
meson-gxl-s805x-p241: 1 failed lab
defconfig:
gcc-8:
msm8998-mtp: 1 failed lab
r8a7795-salvator-x: 1 failed lab
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8:
meson-gxl-s905d-p230: 1 failed lab
meson-gxm-q200: 1 failed lab
arm:
omap2plus_defconfig:
gcc-8:
omap3-beagle-xm: 1 failed lab
sama5_defconfig:
gcc-8:
at91-sama5d4_xplained: 1 failed lab
Offline Platforms:
arm64:
defconfig+CONFIG_RANDOMIZE_BASE=y:
gcc-8
meson-axg-s400: 1 offline lab
defconfig:
gcc-8
meson-axg-s400: 1 offline lab
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8
meson-axg-s400: 1 offline lab
arm:
sunxi_defconfig:
gcc-8
sun5i-r8-chip: 1 offline lab
multi_v7_defconfig:
gcc-8
qcom-apq8064-cm-qs600: 1 offline lab
sun5i-r8-chip: 1 offline lab
qcom_defconfig:
gcc-8
qcom-apq8064-cm-qs600: 1 offline lab
davinci_all_defconfig:
gcc-8
dm365evm,legacy: 1 offline lab
---
For more info write to <info@kernelci.org>
reply other threads:[~2020-01-24 20:13 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=5e2b4ff3.1c69fb81.22b9c.49bb@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.