From: "kernelci.org bot" <bot@kernelci.org>
To: stable@vger.kernel.org
Subject: stable-rc/linux-4.9.y boot: 104 boots: 1 failed, 96 passed with 6 offline, 1 conflict (v4.9.205)
Date: Fri, 29 Nov 2019 11:05:59 -0800 (PST) [thread overview]
Message-ID: <5de16c17.1c69fb81.3d68b.857e@mx.google.com> (raw)
stable-rc/linux-4.9.y boot: 104 boots: 1 failed, 96 passed with 6 offline, 1 conflict (v4.9.205)
Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.9.y/kernel/v4.9.205/
Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.9.y/kernel/v4.9.205/
Tree: stable-rc
Branch: linux-4.9.y
Git Describe: v4.9.205
Git Commit: 6620daa748cbad3de5824143e107a9a545f3c1df
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Tested: 54 unique boards, 20 SoC families, 14 builds out of 197
Boot Regressions Detected:
arm:
davinci_all_defconfig:
gcc-8:
da850-evm:
lab-baylibre-seattle: new failure (last pass: v4.9.203-152-g3bbfc6b1c25b)
dm365evm,legacy:
lab-baylibre-seattle: new failure (last pass: v4.9.203-152-g3bbfc6b1c25b)
Boot Failure Detected:
arm:
sunxi_defconfig:
gcc-8:
sun7i-a20-olinuxino-lime2: 1 failed lab
Offline Platforms:
arm:
davinci_all_defconfig:
gcc-8
da850-evm: 1 offline lab
dm365evm,legacy: 1 offline lab
exynos_defconfig:
gcc-8
exynos5800-peach-pi: 1 offline lab
sunxi_defconfig:
gcc-8
sun7i-a20-bananapi: 1 offline lab
multi_v7_defconfig:
gcc-8
exynos5800-peach-pi: 1 offline lab
sun7i-a20-bananapi: 1 offline lab
Conflicting Boot Failure Detected: (These likely are not failures as other labs are reporting PASS. Needs review.)
arm:
omap2plus_defconfig:
omap4-panda:
lab-collabora: PASS (gcc-8)
lab-baylibre-seattle: PASS (gcc-8)
lab-baylibre: FAIL (gcc-8)
---
For more info write to <info@kernelci.org>
reply other threads:[~2019-11-29 19:06 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=5de16c17.1c69fb81.3d68b.857e@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).