All of lore.kernel.org
 help / color / mirror / Atom feed
From: "kernelci.org bot" <bot@kernelci.org>
To: linux-next@vger.kernel.org
Subject: next/master boot: 276 boots: 7 failed, 256 passed with 6 offline, 5 untried/unknown, 2 conflicts (next-20200417)
Date: Fri, 17 Apr 2020 09:56:45 -0700 (PDT)	[thread overview]
Message-ID: <5e99dfcd.1c69fb81.34e3b.81be@mx.google.com> (raw)

next/master boot: 276 boots: 7 failed, 256 passed with 6 offline, 5 untried/unknown, 2 conflicts (next-20200417)

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

Tree: next
Branch: master
Git Describe: next-20200417
Git Commit: ea16390b6f2d61f0db6fadc8c512c012c1edd1b9
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 107 unique boards, 24 SoC families, 30 builds out of 228

Boot Regressions Detected:

arm:

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

arm64:

    defconfig:
        gcc-8:
          apq8096-db820c:
              lab-bjorn: failing since 16 days (last pass: next-20200330 - first fail: next-20200401)
          meson-g12b-a311d-khadas-vim3:
              lab-baylibre: new failure (last pass: next-20200416)
          meson-gxl-s905d-p230:
              lab-baylibre: new failure (last pass: next-20200416)

    defconfig+CONFIG_CPU_BIG_ENDIAN=y:
        gcc-8:
          meson-axg-s400:
              lab-baylibre-seattle: new failure (last pass: next-20200416)
          meson-gxbb-p200:
              lab-baylibre: new failure (last pass: next-20200416)

    defconfig+CONFIG_RANDOMIZE_BASE=y:
        gcc-8:
          meson-axg-s400:
              lab-baylibre-seattle: new failure (last pass: next-20200416)
          meson-gxl-s805x-p241:
              lab-baylibre: failing since 1 day (last pass: next-20200414 - first fail: next-20200416)
          meson-gxl-s905d-p230:
              lab-baylibre: new failure (last pass: next-20200416)

i386:

    i386_defconfig:
        gcc-8:
          qemu_i386:
              lab-baylibre: new failure (last pass: next-20200416)

riscv:

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

Boot Failures Detected:

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

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

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

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

    defconfig:
        gcc-8:
            apq8096-db820c: 1 failed lab
            meson-gxl-s905d-p230: 1 failed lab

Offline Platforms:

arm:

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

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

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

arm64:

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

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

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

arm:
    multi_v7_defconfig+CONFIG_SMP=n:
        sun7i-a20-cubieboard2:
            lab-baylibre: PASS (gcc-8)
            lab-clabbe: FAIL (gcc-8)

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

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

                 reply	other threads:[~2020-04-17 16:56 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=5e99dfcd.1c69fb81.34e3b.81be@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.