From: "kernelci.org bot" <bot@kernelci.org>
To: stable@vger.kernel.org
Subject: stable-rc/linux-4.19.y boot: 98 boots: 9 failed, 65 passed with 16 offline, 8 conflicts (v4.19.1-362-gc881caaeb264)
Date: Sun, 11 Nov 2018 20:10:02 -0800 (PST) [thread overview]
Message-ID: <5be8fd1a.1c69fb81.6a368.0d01@mx.google.com> (raw)
stable-rc/linux-4.19.y boot: 98 boots: 9 failed, 65 passed with 16 offline, 8 conflicts (v4.19.1-362-gc881caaeb264)
Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.19.y/kernel/v4.19.1-362-gc881caaeb264/
Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.19.y/kernel/v4.19.1-362-gc881caaeb264/
Tree: stable-rc
Branch: linux-4.19.y
Git Describe: v4.19.1-362-gc881caaeb264
Git Commit: c881caaeb264eb22581247c54c007a0bd9e6cd19
Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Tested: 56 unique boards, 21 SoC families, 15 builds out of 186
Boot Regressions Detected:
arm:
bcm2835_defconfig:
bcm2837-rpi-3-b:
lab-baylibre: new failure (last pass: v4.19.1)
multi_v7_defconfig:
imx6q-sabrelite:
lab-baylibre: new failure (last pass: v4.19.1)
meson8b-odroidc1:
lab-baylibre: new failure (last pass: v4.19.1)
qemu:
lab-baylibre: new failure (last pass: v4.19.1)
sun8i-h2-plus-libretech-all-h3-cc:
lab-baylibre: new failure (last pass: v4.19.1)
sun8i-h3-libretech-all-h3-cc:
lab-baylibre: new failure (last pass: v4.19.1)
sunxi_defconfig:
sun8i-h2-plus-libretech-all-h3-cc:
lab-baylibre: new failure (last pass: v4.19.1)
sun8i-h3-libretech-all-h3-cc:
lab-baylibre: new failure (last pass: v4.19.1)
vexpress_defconfig:
qemu:
lab-baylibre: new failure (last pass: v4.19.1)
arm64:
defconfig:
bcm2837-rpi-3-b:
lab-baylibre: new failure (last pass: v4.19.1)
meson-gxbb-p200:
lab-baylibre: new failure (last pass: v4.19.1)
meson-gxl-s905x-khadas-vim:
lab-baylibre: new failure (last pass: v4.19.1)
meson-gxl-s905x-libretech-cc:
lab-baylibre: new failure (last pass: v4.19.1)
qemu:
lab-baylibre: new failure (last pass: v4.19.1)
sun50i-h5-libretech-all-h3-cc:
lab-baylibre: new failure (last pass: v4.19.1)
x86:
x86_64_defconfig:
qemu:
lab-baylibre: new failure (last pass: v4.19.1)
Boot Failures Detected:
arm:
bcm2835_defconfig
bcm2837-rpi-3-b: 1 failed lab
sunxi_defconfig
sun8i-h2-plus-libretech-all-h3-cc: 1 failed lab
sun8i-h3-libretech-all-h3-cc: 1 failed lab
multi_v7_defconfig
imx6q-sabrelite: 1 failed lab
sun8i-h2-plus-libretech-all-h3-cc: 1 failed lab
sun8i-h3-libretech-all-h3-cc: 1 failed lab
arm64:
defconfig
meson-gxbb-nanopi-k2: 1 failed lab
meson-gxl-s905x-libretech-cc: 1 failed lab
sun50i-h5-libretech-all-h3-cc: 1 failed lab
Offline Platforms:
arm:
omap2plus_defconfig:
am335x-boneblack: 1 offline lab
sunxi_defconfig:
sun5i-r8-chip: 1 offline lab
tegra_defconfig:
tegra124-jetson-tk1: 1 offline lab
bcm2835_defconfig:
bcm2835-rpi-b: 1 offline lab
sama5_defconfig:
at91-sama5d4_xplained: 1 offline lab
multi_v7_defconfig:
alpine-db: 1 offline lab
am335x-boneblack: 1 offline lab
at91-sama5d4_xplained: 1 offline lab
socfpga_cyclone5_de0_sockit: 1 offline lab
sun5i-r8-chip: 1 offline lab
tegra124-jetson-tk1: 1 offline lab
arm64:
defconfig:
apq8016-sbc: 1 offline lab
juno-r2: 1 offline lab
meson-gxl-s905d-p230: 1 offline lab
meson-gxl-s905x-p212: 1 offline lab
mt7622-rfb1: 1 offline lab
Conflicting Boot Failures Detected: (These likely are not failures as other labs are reporting PASS. Needs review.)
arm:
multi_v7_defconfig:
qemu:
lab-baylibre: FAIL
lab-mhart: PASS
meson8b-odroidc1:
lab-baylibre: FAIL
lab-baylibre-seattle: PASS
vexpress_defconfig:
qemu:
lab-baylibre: FAIL
lab-mhart: PASS
arm64:
defconfig:
meson-gxl-s905x-khadas-vim:
lab-baylibre: FAIL
lab-baylibre-seattle: PASS
qemu:
lab-baylibre: FAIL
lab-mhart: PASS
bcm2837-rpi-3-b:
lab-baylibre: FAIL
lab-mhart: PASS
lab-baylibre-seattle: PASS
meson-gxbb-p200:
lab-baylibre: FAIL
lab-baylibre-seattle: PASS
x86:
x86_64_defconfig:
qemu:
lab-baylibre: FAIL
lab-mhart: PASS
---
For more info write to <info@kernelci.org>
reply other threads:[~2018-11-12 14:01 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=5be8fd1a.1c69fb81.6a368.0d01@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