linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "kernelci.org bot" <bot@kernelci.org>
To: linux-next@vger.kernel.org
Subject: next/pending-fixes boot: 274 boots: 2 failed, 265 passed with 7 offline (v5.4-4416-gf0d11b9fd5c9)
Date: Tue, 26 Nov 2019 18:47:21 -0800 (PST)	[thread overview]
Message-ID: <5ddde3b9.1c69fb81.bf773.b37e@mx.google.com> (raw)

next/pending-fixes boot: 274 boots: 2 failed, 265 passed with 7 offline (v5.4-4416-gf0d11b9fd5c9)

Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/pending-fixes/kernel/v5.4-4416-gf0d11b9fd5c9/
Full Build Summary: https://kernelci.org/build/next/branch/pending-fixes/kernel/v5.4-4416-gf0d11b9fd5c9/

Tree: next
Branch: pending-fixes
Git Describe: v5.4-4416-gf0d11b9fd5c9
Git Commit: f0d11b9fd5c9014d623f559c22c82a9353bc32cc
Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 98 unique boards, 26 SoC families, 28 builds out of 216

Boot Failures Detected:

arm64:
    defconfig+CONFIG_RANDOMIZE_BASE=y:
        gcc-8:
            meson-gxl-s805x-libretech-ac: 1 failed lab

    defconfig+CONFIG_CPU_BIG_ENDIAN=y:
        gcc-8:
            meson-gxl-s805x-libretech-ac: 1 failed lab

Offline Platforms:

arm:

    davinci_all_defconfig:
        gcc-8
            dm365evm,legacy: 1 offline lab

    exynos_defconfig:
        gcc-8
            exynos5800-peach-pi: 1 offline lab

    sunxi_defconfig:
        gcc-8
            sun7i-a20-bananapi: 1 offline lab

    multi_v7_defconfig:
        gcc-8
            exynos5800-peach-pi: 1 offline lab
            mt7623n-bananapi-bpi-r2: 1 offline lab
            sun7i-a20-bananapi: 1 offline lab

arm64:

    defconfig+CONFIG_RANDOMIZE_BASE=y:
        gcc-8
            meson-axg-s400: 1 offline lab

---
For more info write to <info@kernelci.org>

                 reply	other threads:[~2019-11-27  2:47 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=5ddde3b9.1c69fb81.bf773.b37e@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).