From: "kernelci.org bot" <bot@kernelci.org>
To: linux-next@vger.kernel.org
Subject: next/master boot: 256 boots: 11 failed, 236 passed with 4 offline, 5 untried/unknown (next-20200519)
Date: Tue, 19 May 2020 21:01:53 -0700 (PDT) [thread overview]
Message-ID: <5ec4abb1.1c69fb81.71007.3cb6@mx.google.com> (raw)
******************************************
* WARNING: Boot tests are now deprecated *
******************************************
As kernelci.org is expanding its functional testing capabilities, the concept
of boot testing is now deprecated. Boot results are scheduled to be dropped on
*5th June 2020*. The full schedule for boot tests deprecation is available on
this GitHub issue: https://github.com/kernelci/kernelci-backend/issues/238
The new equivalent is the *baseline* test suite which also runs sanity checks
using dmesg and bootrr: https://github.com/kernelci/bootrr
See the *baseline results for this kernel revision* on this page:
https://kernelci.org/test/job/next/branch/master/kernel/next-20200519/plan/baseline/
-------------------------------------------------------------------------------
next/master boot: 256 boots: 11 failed, 236 passed with 4 offline, 5 untried/unknown (next-20200519)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20200519/
Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20200519/
Tree: next
Branch: master
Git Describe: next-20200519
Git Commit: fb57b1fabcb28f358901b2df90abd2b48abc1ca8
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 106 unique boards, 26 SoC families, 30 builds out of 221
Boot Regressions Detected:
arm:
omap2plus_defconfig:
gcc-8:
omap3-beagle:
lab-baylibre-seattle: failing since 5 days (last pass: next-20200501 - first fail: next-20200514)
omap3-beagle-xm:
lab-baylibre: failing since 5 days (last pass: next-20200501 - first fail: next-20200514)
omap4-panda:
lab-baylibre-seattle: failing since 5 days (last pass: next-20200501 - first fail: next-20200514)
sama5_defconfig:
gcc-8:
at91-sama5d4_xplained:
lab-baylibre: failing since 92 days (last pass: next-20200214 - first fail: next-20200217)
sunxi_defconfig:
gcc-8:
sun4i-a10-olinuxino-lime:
lab-baylibre: new failure (last pass: next-20200515)
versatile_defconfig:
gcc-8:
versatile-pb:
lab-collabora: failing since 1 day (last pass: next-20200515 - first fail: next-20200518)
arm64:
defconfig:
gcc-8:
hip07-d05:
lab-collabora: new failure (last pass: next-20200518)
riscv:
defconfig:
gcc-8:
sifive_fu540:
lab-baylibre-seattle: failing since 53 days (last pass: next-20200326 - first fail: next-20200327)
Boot Failures Detected:
riscv:
defconfig:
gcc-8:
sifive_fu540: 1 failed lab
arm:
omap2plus_defconfig:
gcc-8:
omap3-beagle: 1 failed lab
omap3-beagle-xm: 1 failed lab
omap4-panda: 3 failed labs
multi_v7_defconfig:
gcc-8:
bcm2836-rpi-2-b: 1 failed lab
sama5_defconfig:
gcc-8:
at91-sama5d4_xplained: 1 failed lab
arm64:
defconfig+CONFIG_RANDOMIZE_BASE=y:
gcc-8:
mt7622-rfb1: 1 failed lab
defconfig:
gcc-8:
mt7622-rfb1: 1 failed lab
sm8150-mtp: 1 failed lab
Offline Platforms:
arm:
multi_v7_defconfig:
gcc-8
exynos5800-peach-pi: 1 offline lab
qcom-apq8064-cm-qs600: 1 offline lab
stih410-b2120: 1 offline lab
exynos_defconfig:
gcc-8
exynos5800-peach-pi: 1 offline lab
---
For more info write to <info@kernelci.org>
reply other threads:[~2020-05-20 4: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=5ec4abb1.1c69fb81.71007.3cb6@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).