stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "kernelci.org bot" <bot@kernelci.org>
To: stable@vger.kernel.org
Subject: stable-rc/linux-4.9.y boot: 80 boots: 0 failed, 72 passed with 5 offline, 3 untried/unknown (v4.9.222-19-g7d23d52af97e)
Date: Fri, 08 May 2020 12:09:13 -0700 (PDT)	[thread overview]
Message-ID: <5eb5ae59.1c69fb81.99bdb.70b3@mx.google.com> (raw)

stable-rc/linux-4.9.y boot: 80 boots: 0 failed, 72 passed with 5 offline, 3 untried/unknown (v4.9.222-19-g7d23d52af97e)

Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.9.y/kernel/v4.9.222-19-g7d23d52af97e/
Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.9.y/kernel/v4.9.222-19-g7d23d52af97e/

Tree: stable-rc
Branch: linux-4.9.y
Git Describe: v4.9.222-19-g7d23d52af97e
Git Commit: 7d23d52af97eef655fac0057e12d85ce7d4894c3
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Tested: 49 unique boards, 16 SoC families, 18 builds out of 196

Boot Regressions Detected:

arm:

    multi_v7_defconfig:
        gcc-8:
          sun7i-a20-cubieboard2:
              lab-clabbe: new failure (last pass: v4.9.222)

    qcom_defconfig:
        gcc-8:
          qcom-apq8064-cm-qs600:
              lab-baylibre-seattle: failing since 90 days (last pass: v4.9.213 - first fail: v4.9.213-37-g860ec95da9ad)

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

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

                 reply	other threads:[~2020-05-08 19:09 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=5eb5ae59.1c69fb81.99bdb.70b3@mx.google.com \
    --to=bot@kernelci.org \
    --cc=stable@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).