From: "kernelci.org bot" <bot@kernelci.org>
To: linux-next@vger.kernel.org
Subject: next/pending-fixes boot: 259 boots: 2 failed, 246 passed with 8 offline, 2 untried/unknown, 1 conflict (v5.4-rc5-311-g2e788f1fd131)
Date: Tue, 29 Oct 2019 21:21:09 -0700 (PDT) [thread overview]
Message-ID: <5db90fb5.1c69fb81.bbea8.9b75@mx.google.com> (raw)
next/pending-fixes boot: 259 boots: 2 failed, 246 passed with 8 offline, 2 untried/unknown, 1 conflict (v5.4-rc5-311-g2e788f1fd131)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/pending-fixes/kernel/v5.4-rc5-311-g2e788f1fd131/
Full Build Summary: https://kernelci.org/build/next/branch/pending-fixes/kernel/v5.4-rc5-311-g2e788f1fd131/
Tree: next
Branch: pending-fixes
Git Describe: v5.4-rc5-311-g2e788f1fd131
Git Commit: 2e788f1fd13187860120cd3bb215628e5a086f02
Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 94 unique boards, 26 SoC families, 27 builds out of 215
Boot Failures Detected:
arm64:
defconfig+CONFIG_RANDOMIZE_BASE=y:
gcc-8:
meson-gxl-s805x-libretech-ac: 1 failed lab
defconfig:
gcc-8:
apq8096-db820c: 1 failed lab
Offline Platforms:
riscv:
defconfig:
gcc-8
sifive_fu540: 1 offline lab
arm:
multi_v7_defconfig:
gcc-8
qcom-apq8064-cm-qs600: 1 offline lab
sun5i-r8-chip: 1 offline lab
sun7i-a20-bananapi: 1 offline lab
sunxi_defconfig:
gcc-8
sun5i-r8-chip: 1 offline lab
sun7i-a20-bananapi: 1 offline lab
davinci_all_defconfig:
gcc-8
dm365evm,legacy: 1 offline lab
qcom_defconfig:
gcc-8
qcom-apq8064-cm-qs600: 1 offline lab
Conflicting Boot Failure Detected: (These likely are not failures as other labs are reporting PASS. Needs review.)
arm:
multi_v7_defconfig:
omap3-beagle-xm:
lab-baylibre-seattle: PASS (gcc-8)
lab-baylibre: FAIL (gcc-8)
---
For more info write to <info@kernelci.org>
reply other threads:[~2019-10-30 4:21 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=5db90fb5.1c69fb81.bbea8.9b75@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.