From: "kernelci.org bot" <bot@kernelci.org>
To: stable@vger.kernel.org
Subject: stable-rc/linux-5.0.y boot: 123 boots: 10 failed, 112 passed with 1 conflict (v5.0.10)
Date: Sat, 27 Apr 2019 07:31:30 -0700 (PDT) [thread overview]
Message-ID: <5cc467c2.1c69fb81.c848d.d246@mx.google.com> (raw)
stable-rc/linux-5.0.y boot: 123 boots: 10 failed, 112 passed with 1 conflict (v5.0.10)
Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-5.0.y/kernel/v5.0.10/
Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-5.0.y/kernel/v5.0.10/
Tree: stable-rc
Branch: linux-5.0.y
Git Describe: v5.0.10
Git Commit: d3da1f09fff27b3ae5908119dab312b9baec09e0
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Tested: 73 unique boards, 24 SoC families, 14 builds out of 208
Boot Regressions Detected:
arm:
multi_v7_defconfig:
gcc-7:
stih410-b2120:
lab-baylibre-seattle: new failure (last pass: v5.0.9-117-ge428bc9cd366)
omap2plus_defconfig:
gcc-7:
omap3-beagle-xm:
lab-baylibre: new failure (last pass: v5.0.9-44-g068df96fc0d7)
Boot Failures Detected:
arm:
multi_v7_defconfig:
gcc-7:
bcm4708-smartrg-sr400ac: 1 failed lab
bcm72521-bcm97252sffe: 1 failed lab
bcm7445-bcm97445c: 1 failed lab
stih410-b2120: 1 failed lab
sun4i-a10-cubieboard: 1 failed lab
sun7i-a20-bananapi: 1 failed lab
sun7i-a20-cubietruck: 1 failed lab
tegra124-nyan-big: 1 failed lab
omap2plus_defconfig:
gcc-7:
omap3-beagle-xm: 1 failed lab
tegra_defconfig:
gcc-7:
tegra124-nyan-big: 1 failed lab
Conflicting Boot Failure Detected: (These likely are not failures as other labs are reporting PASS. Needs review.)
arm:
multi_v7_defconfig:
exynos5800-peach-pi:
lab-baylibre-seattle: FAIL (gcc-7)
lab-collabora: PASS (gcc-7)
---
For more info write to <info@kernelci.org>
reply other threads:[~2019-04-27 14:31 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=5cc467c2.1c69fb81.c848d.d246@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.