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: 104 boots: 17 failed, 86 passed with 1 untried/unknown (next-20200220)
Date: Thu, 20 Feb 2020 01:53:08 -0800 (PST)	[thread overview]
Message-ID: <5e4e5704.1c69fb81.442fd.7469@mx.google.com> (raw)

next/master boot: 104 boots: 17 failed, 86 passed with 1 untried/unknown (next-20200220)

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

Tree: next
Branch: master
Git Describe: next-20200220
Git Commit: f4aba10148cd290bbbf4d0efae0e9789a13c2778
Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 49 unique boards, 11 SoC families, 8 builds out of 41

Boot Regressions Detected:

arm:

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

    sunxi_defconfig:
        gcc-8:
          sun7i-a20-cubieboard2:
              lab-clabbe: failing since 5 days (last pass: next-20200212 - first fail: next-20200214)
              lab-baylibre: failing since 5 days (last pass: next-20200212 - first fail: next-20200214)
          sun7i-a20-olinuxino-lime2:
              lab-baylibre: failing since 5 days (last pass: next-20200212 - first fail: next-20200214)
          sun8i-a33-olinuxino:
              lab-clabbe: failing since 5 days (last pass: next-20200212 - first fail: next-20200214)
          sun8i-a83t-bananapi-m3:
              lab-clabbe: failing since 5 days (last pass: next-20200211 - first fail: next-20200214)
          sun8i-h2-plus-libretech-all-h3-cc:
              lab-baylibre: failing since 5 days (last pass: next-20200212 - first fail: next-20200214)
          sun8i-h2-plus-orangepi-r1:
              lab-baylibre: failing since 5 days (last pass: next-20200207 - first fail: next-20200214)
          sun8i-h2-plus-orangepi-zero:
              lab-baylibre: failing since 5 days (last pass: next-20200212 - first fail: next-20200214)
          sun8i-h3-orangepi-pc:
              lab-clabbe: failing since 5 days (last pass: next-20200212 - first fail: next-20200214)

arm64:

    defconfig:
        gcc-8:
          rk3399-gru-kevin:
              lab-collabora: failing since 5 days (last pass: next-20200213 - first fail: next-20200214)

    defconfig+CONFIG_RANDOMIZE_BASE=y:
        gcc-8:
          meson-gxl-s805x-libretech-ac:
              lab-baylibre: new failure (last pass: next-20200219)
          rk3399-gru-kevin:
              lab-collabora: new failure (last pass: next-20200213)
          sun50i-h6-pine-h64-model-b:
              lab-baylibre: new failure (last pass: next-20200219)

Boot Failures Detected:

arm:
    sunxi_defconfig:
        gcc-8:
            sun7i-a20-cubieboard2: 2 failed labs
            sun7i-a20-olinuxino-lime2: 1 failed lab
            sun8i-a33-olinuxino: 1 failed lab
            sun8i-a83t-bananapi-m3: 1 failed lab
            sun8i-h2-plus-libretech-all-h3-cc: 1 failed lab
            sun8i-h2-plus-orangepi-r1: 1 failed lab
            sun8i-h2-plus-orangepi-zero: 1 failed lab
            sun8i-h3-libretech-all-h3-cc: 1 failed lab
            sun8i-h3-orangepi-pc: 1 failed lab

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

arm64:
    defconfig:
        gcc-8:
            rk3399-gru-kevin: 1 failed lab
            rk3399-puma-haikou: 1 failed lab

    defconfig+CONFIG_RANDOMIZE_BASE=y:
        gcc-8:
            meson-gxl-s805x-libretech-ac: 1 failed lab
            rk3399-gru-kevin: 1 failed lab
            rk3399-puma-haikou: 1 failed lab

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

                 reply	other threads:[~2020-02-20  9:53 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=5e4e5704.1c69fb81.442fd.7469@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.