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.19.y boot: 110 boots: 0 failed, 108 passed with 1 offline, 1 conflict (v4.19.16-100-ge43bc298813d)
Date: Mon, 21 Jan 2019 10:11:16 -0800 (PST)	[thread overview]
Message-ID: <5c460b44.1c69fb81.ff117.9f2c@mx.google.com> (raw)

stable-rc/linux-4.19.y boot: 110 boots: 0 failed, 108 passed with 1 offline, 1 conflict (v4.19.16-100-ge43bc298813d)

Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.19.y/kernel/v4.19.16-100-ge43bc298813d/
Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.19.y/kernel/v4.19.16-100-ge43bc298813d/

Tree: stable-rc
Branch: linux-4.19.y
Git Describe: v4.19.16-100-ge43bc298813d
Git Commit: e43bc298813db3fa0101865a4bd46c3654825820
Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Tested: 60 unique boards, 22 SoC families, 12 builds out of 202

Boot Regressions Detected:

arm64:

    defconfig:
        meson-gxl-s905x-khadas-vim:
            lab-baylibre-seattle: new failure (last pass: v4.19.16)

Offline Platforms:

arm64:

    defconfig:
        rk3399-firefly: 1 offline lab

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

arm64:

    defconfig:
        meson-gxl-s905x-khadas-vim:
            lab-baylibre: PASS
            lab-baylibre-seattle: FAIL

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

                 reply	other threads:[~2019-01-21 18: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=5c460b44.1c69fb81.ff117.9f2c@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).