public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: "kernelci.org bot" <bot@kernelci•org>
To: linux-next@vger•kernel.org
Subject: next/master boot: 267 boots: 9 failed, 243 passed with 5 offline, 7 untried/unknown, 3 conflicts (next-20200505)
Date: Tue, 05 May 2020 12:11:35 -0700 (PDT)	[thread overview]
Message-ID: <5eb1ba67.1c69fb81.6f314.97cc@mx.google.com> (raw)

next/master boot: 267 boots: 9 failed, 243 passed with 5 offline, 7 untried/unknown, 3 conflicts (next-20200505)

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

Tree: next
Branch: master
Git Describe: next-20200505
Git Commit: 7def1ef0f72c3ebe3e42467d2f73c4e56153fa49
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 105 unique boards, 25 SoC families, 31 builds out of 231

Boot Regressions Detected:

arm:

    sama5_defconfig:
        gcc-8:
          at91-sama5d4_xplained:
              lab-baylibre: failing since 77 days (last pass: next-20200214 - first fail: next-20200217)

arm64:

    defconfig:
        clang-9:
          sm8150-mtp:
              lab-bjorn: new failure (last pass: next-20200430)
        gcc-8:
          sun50i-a64-pine64-plus:
              lab-baylibre: new failure (last pass: next-20200504)

    defconfig+CONFIG_CPU_BIG_ENDIAN=y:
        gcc-8:
          meson-gxbb-p200:
              lab-baylibre: failing since 1 day (last pass: next-20200501 - first fail: next-20200504)
          sun50i-a64-pine64-plus:
              lab-baylibre: new failure (last pass: next-20200504)

    defconfig+CONFIG_RANDOMIZE_BASE=y:
        gcc-8:
          sun50i-a64-pine64-plus:
              lab-baylibre: new failure (last pass: next-20200504)

i386:

    i386_defconfig:
        gcc-8:
          qemu_i386:
              lab-collabora: new failure (last pass: next-20200504)

riscv:

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

x86_64:

    x86_64_defconfig:
        gcc-8:
          qemu_x86_64:
              lab-collabora: new failure (last pass: next-20200504)

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
            sun50i-a64-pine64-plus: 1 failed lab

    defconfig+CONFIG_CPU_BIG_ENDIAN=y:
        gcc-8:
            meson-gxbb-p200: 1 failed lab

arm:
    sama5_defconfig:
        gcc-8:
            at91-sama5d4_xplained: 1 failed lab

    multi_v7_defconfig:
        gcc-8:
            bcm2836-rpi-2-b: 1 failed lab

    allmodconfig:
        gcc-8:
            stm32mp157c-dk2: 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

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

Conflicting Boot Failures Detected: (These likely are not failures as other labs are reporting PASS. Needs review.)

i386:
    i386_defconfig:
        qemu_i386:
            lab-baylibre: PASS (gcc-8)
            lab-collabora: FAIL (gcc-8)

x86_64:
    x86_64_defconfig:
        qemu_x86_64:
            lab-baylibre: PASS (gcc-8)
            lab-collabora: FAIL (gcc-8)

    x86_64_defconfig+kvm_guest:
        qemu_x86_64:
            lab-baylibre: PASS (gcc-8)
            lab-collabora: FAIL (gcc-8)

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

                 reply	other threads:[~2020-05-05 19:11 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=5eb1ba67.1c69fb81.6f314.97cc@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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox