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: 279 boots: 6 failed, 261 passed with 5 offline, 6 untried/unknown, 1 conflict (next-20200415)
Date: Wed, 15 Apr 2020 05:23:08 -0700 (PDT)	[thread overview]
Message-ID: <5e96fcac.1c69fb81.b56d3.71c8@mx.google.com> (raw)

next/master boot: 279 boots: 6 failed, 261 passed with 5 offline, 6 untried/unknown, 1 conflict (next-20200415)

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

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

Boot Regressions Detected:

arm:

    multi_v7_defconfig:
        gcc-8:
          am335x-boneblack:
              lab-baylibre: new failure (last pass: next-20200414)

    multi_v7_defconfig+CONFIG_EFI=y+CONFIG_ARM_LPAE=y:
        gcc-8:
          exynos5422-odroidxu3:
              lab-collabora: new failure (last pass: next-20200414)

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

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

arm64:

    defconfig:
        gcc-8:
          apq8096-db820c:
              lab-bjorn: failing since 13 days (last pass: next-20200330 - first fail: next-20200401)
          meson-axg-s400:
              lab-baylibre-seattle: new failure (last pass: next-20200414)
          meson-g12b-a311d-khadas-vim3:
              lab-baylibre: new failure (last pass: next-20200414)

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

    defconfig+CONFIG_RANDOMIZE_BASE=y:
        gcc-8:
          meson-axg-s400:
              lab-baylibre-seattle: new failure (last pass: next-20200414)

riscv:

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

x86_64:

    x86_64_defconfig+kselftest:
        gcc-8:
          qemu_x86_64:
              lab-baylibre: new failure (last pass: next-20200414)

Boot Failures Detected:

arm:
    multi_v7_defconfig+CONFIG_EFI=y+CONFIG_ARM_LPAE=y:
        gcc-8:
            exynos5422-odroidxu3: 1 failed lab

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

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

arm64:
    defconfig:
        gcc-8:
            apq8096-db820c: 1 failed lab
            meson-g12b-a311d-khadas-vim3: 1 failed lab

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

Offline Platforms:

arm:

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

arm64:

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

    defconfig:
        gcc-8
            meson-axg-s400: 1 offline lab

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

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

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

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

                 reply	other threads:[~2020-04-15 12:23 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=5e96fcac.1c69fb81.b56d3.71c8@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.