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/master boot: 231 boots: 10 failed, 209 passed with 6 offline, 6 untried/unknown (next-20200508)
Date: Fri, 08 May 2020 12:47:24 -0700 (PDT)	[thread overview]
Message-ID: <5eb5b74c.1c69fb81.6bd87.a423@mx.google.com> (raw)

next/master boot: 231 boots: 10 failed, 209 passed with 6 offline, 6 untried/unknown (next-20200508)

Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20200508/
Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20200508/

Tree: next
Branch: master
Git Describe: next-20200508
Git Commit: 30e2206e11ce27ae910cc0dab21472429e400a87
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 95 unique boards, 23 SoC families, 29 builds out of 231

Boot Regressions Detected:

arm:

    multi_v7_defconfig:
        gcc-8:
          tegra124-jetson-tk1:
              lab-collabora: failing since 1 day (last pass: next-20200505 - first fail: next-20200507)

    multi_v7_defconfig+CONFIG_EFI=y+CONFIG_ARM_LPAE=y:
        gcc-8:
          tegra124-jetson-tk1:
              lab-collabora: failing since 1 day (last pass: next-20200505 - first fail: next-20200507)

    multi_v7_defconfig+CONFIG_SMP=n:
        gcc-8:
          sun7i-a20-cubieboard2:
              lab-clabbe: new failure (last pass: next-20200507)
          tegra124-jetson-tk1:
              lab-collabora: failing since 1 day (last pass: next-20200505 - first fail: next-20200507)

    tegra_defconfig:
        gcc-8:
          tegra124-jetson-tk1:
              lab-collabora: failing since 1 day (last pass: next-20200505 - first fail: next-20200507)
          tegra30-beaver:
              lab-baylibre-seattle: failing since 1 day (last pass: next-20200505 - first fail: next-20200507)

    versatile_defconfig:
        gcc-8:
          versatile-pb:
              lab-collabora: new failure (last pass: next-20200505)

arm64:

    defconfig:
        clang-9:
          apq8016-sbc:
              lab-bjorn: failing since 1 day (last pass: next-20200505 - first fail: next-20200507)

riscv:

    defconfig:
        gcc-8:
          sifive_fu540:
              lab-baylibre-seattle: failing since 42 days (last pass: next-20200326 - first fail: next-20200327)

Boot Failures Detected:

riscv:
    defconfig:
        gcc-8:
            sifive_fu540: 1 failed lab

arm64:
    defconfig:
        gcc-8:
            mt7622-rfb1: 1 failed lab

    defconfig+CONFIG_RANDOMIZE_BASE=y:
        gcc-8:
            mt7622-rfb1: 1 failed lab

arm:
    tegra_defconfig:
        gcc-8:
            tegra124-jetson-tk1: 1 failed lab
            tegra30-beaver: 1 failed lab

    multi_v7_defconfig:
        gcc-8:
            tegra124-jetson-tk1: 1 failed lab
            tegra30-beaver: 1 failed lab

    multi_v7_defconfig+CONFIG_EFI=y+CONFIG_ARM_LPAE=y:
        gcc-8:
            tegra124-jetson-tk1: 1 failed lab

    multi_v7_defconfig+CONFIG_SMP=n:
        gcc-8:
            tegra124-jetson-tk1: 1 failed lab

Offline Platforms:

arm:

    multi_v7_defconfig:
        gcc-8
            exynos5800-peach-pi: 1 offline lab
            qcom-apq8064-cm-qs600: 1 offline lab
            stih410-b2120: 1 offline lab

    qcom_defconfig:
        gcc-8
            qcom-apq8064-cm-qs600: 1 offline lab

    davinci_all_defconfig:
        gcc-8
            da850-evm: 1 offline lab

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

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

                 reply	other threads:[~2020-05-08 19: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=5eb5b74c.1c69fb81.6bd87.a423@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).