All of lore.kernel.org
 help / color / mirror / Atom feed
From: "kernelci.org bot" <bot@kernelci.org>
To: stable@vger.kernel.org
Subject: stable/linux-4.19.y boot: 118 boots: 1 failed, 114 passed with 1 offline, 1 untried/unknown, 1 conflict (v4.19.10)
Date: Mon, 17 Dec 2018 05:33:07 -0800 (PST)	[thread overview]
Message-ID: <5c17a593.1c69fb81.b0079.0968@mx.google.com> (raw)

stable/linux-4.19.y boot: 118 boots: 1 failed, 114 passed with 1 offline, 1 untried/unknown, 1 conflict (v4.19.10)

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

Tree: stable
Branch: linux-4.19.y
Git Describe: v4.19.10
Git Commit: b23de3254f8cd4166511dfd28a051358a80aa2fa
Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
Tested: 62 unique boards, 23 SoC families, 12 builds out of 202

Boot Regressions Detected:

arm:

    multi_v7_defconfig:
        omap3-beagle-xm:
            lab-baylibre: new failure (last pass: v4.19.9)

arm64:

    defconfig:
        meson-gxbb-p200:
            lab-baylibre: new failure (last pass: v4.19.8)

Boot Failure Detected:

arm:

    multi_v7_defconfig
        omap3-beagle-xm: 1 failed lab

Offline Platforms:

arm:

    multi_v7_defconfig:
        stih410-b2120: 1 offline lab

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

arm64:

    defconfig:
        meson-gxbb-p200:
            lab-baylibre-seattle: PASS
            lab-baylibre: FAIL

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

                 reply	other threads:[~2018-12-17 13:33 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=5c17a593.1c69fb81.b0079.0968@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 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.