From: "kernelci.org bot" <bot@kernelci•org>
To: linux-next@vger•kernel.org
Subject: next/master boot: 225 boots: 2 failed, 218 passed with 1 offline, 2 untried/unknown, 2 conflicts (next-20190611)
Date: Tue, 11 Jun 2019 10:16:34 -0700 (PDT) [thread overview]
Message-ID: <5cffe1f2.1c69fb81.c9f9c.ae59@mx.google.com> (raw)
next/master boot: 225 boots: 2 failed, 218 passed with 1 offline, 2 untried/unknown, 2 conflicts (next-20190611)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20190611/
Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20190611/
Tree: next
Branch: master
Git Describe: next-20190611
Git Commit: f08776cae7f5ab26f0f239b9ec58aa60fdbb9a1a
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 230
Boot Regressions Detected:
arm64:
defconfig:
gcc-8:
meson-gxl-s905x-khadas-vim:
lab-baylibre-seattle: failing since 5 days (last pass: next-20190605 - first fail: next-20190606)
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8:
meson-gxl-s905x-khadas-vim:
lab-baylibre-seattle: failing since 5 days (last pass: next-20190605 - first fail: next-20190606)
Boot Failures Detected:
arm:
multi_v7_defconfig:
gcc-8:
bcm4708-smartrg-sr400ac: 1 failed lab
arm64:
defconfig+CONFIG_RANDOMIZE_BASE=y:
gcc-8:
meson-gxm-khadas-vim2: 1 failed lab
Offline Platforms:
mips:
pistachio_defconfig:
gcc-8
pistachio_marduk: 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:
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-11 17:16 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=5cffe1f2.1c69fb81.c9f9c.ae59@mx.google.com \
--to=bot@kernelci$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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