From: "kernelci.org bot" <bot@kernelci.org>
To: linux-next@vger.kernel.org
Subject: next/pending-fixes boot: 203 boots: 5 failed, 195 passed with 3 offline (v5.2-8386-gdcbf79ebd5fe)
Date: Mon, 15 Jul 2019 04:05:33 -0700 (PDT) [thread overview]
Message-ID: <5d2c5dfd.1c69fb81.02bd.392d@mx.google.com> (raw)
next/pending-fixes boot: 203 boots: 5 failed, 195 passed with 3 offline (v5.2-8386-gdcbf79ebd5fe)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/pending-fixes/kernel/v5.2-8386-gdcbf79ebd5fe/
Full Build Summary: https://kernelci.org/build/next/branch/pending-fixes/kernel/v5.2-8386-gdcbf79ebd5fe/
Tree: next
Branch: pending-fixes
Git Describe: v5.2-8386-gdcbf79ebd5fe
Git Commit: dcbf79ebd5fe67c2a8174d92c9a812b74b11cc48
Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 79 unique boards, 26 SoC families, 20 builds out of 223
Boot Regressions Detected:
arm:
multi_v7_defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8:
armada-xp-openblocks-ax3-4:
lab-baylibre-seattle: failing since 19 days (last pass: v5.2-rc6-99-g690c98f37a5e - first fail: v5.2-rc6-130-gddc352bc91de)
arm64:
defconfig:
gcc-8:
qcs404-evb-4k:
lab-bjorn: failing since 4 days (last pass: v5.2-1383-g58038662df39 - first fail: v5.2-3342-g43c27ecab3ce)
Boot Failures Detected:
arm:
sunxi_defconfig:
gcc-8:
sun7i-a20-bananapi: 1 failed lab
multi_v7_defconfig:
gcc-8:
sun7i-a20-bananapi: 1 failed lab
multi_v7_defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8:
armada-xp-openblocks-ax3-4: 1 failed lab
arm64:
defconfig:
gcc-8:
apq8096-db820c: 1 failed lab
qcs404-evb-4k: 1 failed lab
Offline Platforms:
arm64:
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8
meson-gxbb-odroidc2: 1 offline lab
defconfig:
gcc-8
meson-gxbb-odroidc2: 1 offline lab
defconfig+CONFIG_RANDOMIZE_BASE=y:
gcc-8
meson-gxbb-odroidc2: 1 offline lab
---
For more info write to <info@kernelci.org>
reply other threads:[~2019-07-15 11:05 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=5d2c5dfd.1c69fb81.02bd.392d@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 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.