From: "kernelci.org bot" <bot@kernelci.org>
To: stable@vger.kernel.org
Subject: stable-rc/linux-4.9.y boot: 113 boots: 1 failed, 104 passed with 2 offline, 5 untried/unknown, 1 conflict (v4.9.218-99-gbd51c04713a4)
Date: Thu, 16 Apr 2020 11:33:07 -0700 (PDT) [thread overview]
Message-ID: <5e98a4e3.1c69fb81.5ae1d.20ee@mx.google.com> (raw)
stable-rc/linux-4.9.y boot: 113 boots: 1 failed, 104 passed with 2 offline, 5 untried/unknown, 1 conflict (v4.9.218-99-gbd51c04713a4)
Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.9.y/kernel/v4.9.218-99-gbd51c04713a4/
Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.9.y/kernel/v4.9.218-99-gbd51c04713a4/
Tree: stable-rc
Branch: linux-4.9.y
Git Describe: v4.9.218-99-gbd51c04713a4
Git Commit: bd51c04713a4f34dd89ff3897c11e9bef252825b
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Tested: 60 unique boards, 20 SoC families, 19 builds out of 197
Boot Regressions Detected:
arm:
qcom_defconfig:
gcc-8:
qcom-apq8064-cm-qs600:
lab-baylibre-seattle: failing since 68 days (last pass: v4.9.213 - first fail: v4.9.213-37-g860ec95da9ad)
versatile_defconfig:
gcc-8:
versatile-pb:
lab-collabora: new failure (last pass: v4.9.218-93-g8271444878fc)
x86_64:
x86_64_defconfig:
gcc-8:
qemu_x86_64:
lab-baylibre: new failure (last pass: v4.9.218-93-g8271444878fc)
Boot Failure Detected:
arm:
sama5_defconfig:
gcc-8:
at91-sama5d4_xplained: 1 failed lab
Offline Platforms:
arm:
qcom_defconfig:
gcc-8
qcom-apq8064-cm-qs600: 1 offline lab
multi_v7_defconfig:
gcc-8
qcom-apq8064-cm-qs600: 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:
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-16 18: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=5e98a4e3.1c69fb81.5ae1d.20ee@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).