From: "kernelci.org bot" <bot@kernelci.org>
To: stable@vger.kernel.org
Subject: stable-rc/linux-4.9.y boot: 78 boots: 27 failed, 44 passed with 5 offline, 2 conflicts (v4.9.203)
Date: Mon, 25 Nov 2019 22:38:55 -0800 (PST) [thread overview]
Message-ID: <5ddcc87f.1c69fb81.46d46.52ab@mx.google.com> (raw)
stable-rc/linux-4.9.y boot: 78 boots: 27 failed, 44 passed with 5 offline, 2 conflicts (v4.9.203)
Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.9.y/kernel/v4.9.203/
Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.9.y/kernel/v4.9.203/
Tree: stable-rc
Branch: linux-4.9.y
Git Describe: v4.9.203
Git Commit: a777e9dd40fe85dfd0cc5cb2b6c22a9cd1d08c0d
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Tested: 45 unique boards, 18 SoC families, 14 builds out of 197
Boot Regressions Detected:
arm:
davinci_all_defconfig:
gcc-8:
da850-lcdk:
lab-baylibre: new failure (last pass: v4.9.202-223-gc2ff777d9ae8)
Boot Failures Detected:
i386:
i386_defconfig:
gcc-8:
qemu_i386: 1 failed lab
arm:
multi_v7_defconfig:
gcc-8:
am335x-boneblack: 2 failed labs
imx6q-sabrelite: 1 failed lab
meson8b-odroidc1: 1 failed lab
omap3-beagle-xm: 1 failed lab
qemu_arm-virt-gicv2: 1 failed lab
qemu_arm-virt-gicv3: 1 failed lab
sun4i-a10-olinuxino-lime: 1 failed lab
sun5i-a13-olinuxino-micro: 1 failed lab
sun7i-a20-cubieboard2: 2 failed labs
sun8i-a33-olinuxino: 1 failed lab
sun8i-h3-orangepi-pc: 1 failed lab
tegra124-jetson-tk1: 1 failed lab
tegra_defconfig:
gcc-8:
tegra124-jetson-tk1: 1 failed lab
omap2plus_defconfig:
gcc-8:
am335x-boneblack: 2 failed labs
omap3-beagle-xm: 1 failed lab
davinci_all_defconfig:
gcc-8:
da850-lcdk: 1 failed lab
sunxi_defconfig:
gcc-8:
sun4i-a10-olinuxino-lime: 1 failed lab
sun5i-a13-olinuxino-micro: 1 failed lab
sun7i-a20-cubieboard2: 2 failed labs
sun8i-a33-olinuxino: 1 failed lab
sun8i-h3-orangepi-pc: 1 failed lab
x86_64:
x86_64_defconfig:
gcc-8:
qemu_x86_64: 1 failed lab
Offline Platforms:
arm:
multi_v7_defconfig:
gcc-8
exynos5800-peach-pi: 1 offline lab
sun7i-a20-bananapi: 1 offline lab
exynos_defconfig:
gcc-8
exynos5800-peach-pi: 1 offline lab
davinci_all_defconfig:
gcc-8
dm365evm,legacy: 1 offline lab
sunxi_defconfig:
gcc-8
sun7i-a20-bananapi: 1 offline lab
Conflicting Boot Failures Detected: (These likely are not failures as other labs are reporting PASS. Needs review.)
arm:
multi_v7_defconfig:
omap4-panda:
lab-baylibre-seattle: PASS (gcc-8)
lab-baylibre: FAIL (gcc-8)
omap2plus_defconfig:
omap4-panda:
lab-baylibre-seattle: PASS (gcc-8)
lab-baylibre: FAIL (gcc-8)
---
For more info write to <info@kernelci.org>
reply other threads:[~2019-11-26 6:38 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=5ddcc87f.1c69fb81.46d46.52ab@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.