From: "kernelci.org bot" <bot@kernelci.org>
To: linux-next@vger.kernel.org
Subject: next/pending-fixes boot: 223 boots: 5 failed, 197 passed with 16 offline, 3 untried/unknown, 2 conflicts (v5.2-rc3-336-gfd5c57db249c)
Date: Thu, 06 Jun 2019 05:54:07 -0700 (PDT) [thread overview]
Message-ID: <5cf90cef.1c69fb81.e441d.e4fc@mx.google.com> (raw)
next/pending-fixes boot: 223 boots: 5 failed, 197 passed with 16 offline, 3 untried/unknown, 2 conflicts (v5.2-rc3-336-gfd5c57db249c)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/pending-fixes/kernel/v5.2-rc3-336-gfd5c57db249c/
Full Build Summary: https://kernelci.org/build/next/branch/pending-fixes/kernel/v5.2-rc3-336-gfd5c57db249c/
Tree: next
Branch: pending-fixes
Git Describe: v5.2-rc3-336-gfd5c57db249c
Git Commit: fd5c57db249c77971d11e3cd1cb12d7737bb20da
Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 83 unique boards, 24 SoC families, 20 builds out of 223
Boot Regressions Detected:
arm:
sunxi_defconfig:
gcc-8:
sun8i-h2-plus-libretech-all-h3-cc:
lab-baylibre: failing since 9 days (last pass: v5.2-rc1-444-g4ef1cc845da3 - first fail: v5.2-rc2-257-gb0251876abbf2)
sun8i-h3-libretech-all-h3-cc:
lab-baylibre: failing since 9 days (last pass: v5.2-rc1-444-g4ef1cc845da3 - first fail: v5.2-rc2-257-gb0251876abbf2)
arm64:
defconfig:
gcc-8:
meson-gxl-s905x-khadas-vim:
lab-baylibre-seattle: new failure (last pass: v5.2-rc3-298-gefd8de4f40d0)
lab-baylibre: new failure (last pass: v5.2-rc3-279-g8e8436fc2596)
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8:
meson-gxl-s905x-khadas-vim:
lab-baylibre-seattle: new failure (last pass: v5.2-rc3-298-gefd8de4f40d0)
defconfig+CONFIG_RANDOMIZE_BASE=y:
gcc-8:
meson-gxl-s905x-khadas-vim:
lab-baylibre-seattle: new failure (last pass: v5.2-rc3-298-gefd8de4f40d0)
Boot Failures Detected:
arm:
sunxi_defconfig:
gcc-8:
sun8i-h2-plus-libretech-all-h3-cc: 1 failed lab
sun8i-h3-libretech-all-h3-cc: 1 failed lab
multi_v7_defconfig:
gcc-8:
bcm4708-smartrg-sr400ac: 1 failed lab
arm64:
defconfig:
gcc-8:
meson-gxl-s905x-khadas-vim: 2 failed labs
Offline Platforms:
arm:
bcm2835_defconfig:
gcc-8
bcm2835-rpi-b: 1 offline lab
sama5_defconfig:
gcc-8
at91-sama5d4_xplained: 1 offline lab
at91-sama5d4ek: 1 offline lab
multi_v7_defconfig:
gcc-8
alpine-db: 1 offline lab
at91-sama5d4_xplained: 1 offline lab
at91-sama5d4ek: 1 offline lab
sun5i-r8-chip: 1 offline lab
sunxi_defconfig:
gcc-8
sun5i-r8-chip: 1 offline lab
arm64:
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8
apq8016-sbc: 1 offline lab
juno-r2: 1 offline lab
defconfig:
gcc-8
apq8016-sbc: 1 offline lab
juno-r2: 1 offline lab
mt7622-rfb1: 1 offline lab
defconfig+CONFIG_RANDOMIZE_BASE=y:
gcc-8
apq8016-sbc: 1 offline lab
juno-r2: 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.)
arm64:
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
meson-gxl-s905x-khadas-vim:
lab-baylibre-seattle: FAIL (gcc-8)
lab-baylibre: PASS (gcc-8)
defconfig+CONFIG_RANDOMIZE_BASE=y:
meson-gxl-s905x-khadas-vim:
lab-baylibre-seattle: FAIL (gcc-8)
lab-baylibre: PASS (gcc-8)
---
For more info write to <info@kernelci.org>
reply other threads:[~2019-06-06 12:54 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=5cf90cef.1c69fb81.e441d.e4fc@mx.google.com \
--to=bot@kernelci.org \
--cc=linux-next@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).