From: "kernelci.org bot" <bot@kernelci.org>
To: stable@vger.kernel.org
Subject: stable-rc/linux-4.19.y boot: 133 boots: 1 failed, 113 passed with 13 offline, 5 untried/unknown, 1 conflict (v4.19.122)
Date: Mon, 11 May 2020 10:39:20 -0700 (PDT) [thread overview]
Message-ID: <5eb98dc8.1c69fb81.cbf2f.30ad@mx.google.com> (raw)
stable-rc/linux-4.19.y boot: 133 boots: 1 failed, 113 passed with 13 offline, 5 untried/unknown, 1 conflict (v4.19.122)
Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.19.y/kernel/v4.19.122/
Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.19.y/kernel/v4.19.122/
Tree: stable-rc
Branch: linux-4.19.y
Git Describe: v4.19.122
Git Commit: 033c4ea49a4ba7a2b13aabf3ec755557924a9cda
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Tested: 79 unique boards, 21 SoC families, 20 builds out of 206
Boot Regressions Detected:
arm:
imx_v6_v7_defconfig:
gcc-8:
imx6dl-wandboard_dual:
lab-baylibre-seattle: new failure (last pass: v4.19.121-33-g7ad26f947708)
imx6dl-wandboard_solo:
lab-baylibre-seattle: new failure (last pass: v4.19.121-33-g7ad26f947708)
omap2plus_defconfig:
gcc-8:
omap3-beagle:
lab-baylibre-seattle: new failure (last pass: v4.19.121)
sama5_defconfig:
gcc-8:
at91-sama5d4_xplained:
lab-baylibre: failing since 59 days (last pass: v4.19.108-87-g624c124960e8 - first fail: v4.19.109)
sunxi_defconfig:
gcc-8:
sun8i-h2-plus-orangepi-r1:
lab-baylibre: new failure (last pass: v4.19.121)
tegra_defconfig:
gcc-8:
tegra30-beaver:
lab-baylibre-seattle: new failure (last pass: v4.19.121-33-g7ad26f947708)
versatile_defconfig:
gcc-8:
versatile-pb:
lab-collabora: new failure (last pass: v4.19.121-33-g7ad26f947708)
i386:
i386_defconfig:
gcc-8:
qemu_i386:
lab-baylibre: new failure (last pass: v4.19.121-33-g7ad26f947708)
Boot Failure Detected:
arm:
sama5_defconfig:
gcc-8:
at91-sama5d4_xplained: 1 failed lab
Offline Platforms:
arm:
omap2plus_defconfig:
gcc-8
omap3-beagle: 1 offline lab
tegra_defconfig:
gcc-8
tegra30-beaver: 1 offline lab
multi_v7_defconfig:
gcc-8
exynos5800-peach-pi: 1 offline lab
imx6dl-wandboard_dual: 1 offline lab
imx6dl-wandboard_solo: 1 offline lab
imx6q-wandboard: 1 offline lab
omap3-beagle: 1 offline lab
stih410-b2120: 1 offline lab
tegra30-beaver: 1 offline lab
imx_v6_v7_defconfig:
gcc-8
imx6dl-wandboard_dual: 1 offline lab
imx6dl-wandboard_solo: 1 offline lab
imx6q-wandboard: 1 offline lab
exynos_defconfig:
gcc-8
exynos5800-peach-pi: 1 offline lab
Conflicting Boot Failure Detected: (These likely are not failures as other labs are reporting PASS. Needs review.)
i386:
i386_defconfig:
qemu_i386:
lab-baylibre: FAIL (gcc-8)
lab-collabora: PASS (gcc-8)
---
For more info write to <info@kernelci.org>
reply other threads:[~2020-05-11 17:39 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=5eb98dc8.1c69fb81.cbf2f.30ad@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).