From: "kernelci.org bot" <bot@kernelci.org>
To: linux-next@vger.kernel.org
Subject: next/master boot: 245 boots: 12 failed, 231 passed with 2 offline (next-20200204)
Date: Tue, 04 Feb 2020 09:24:05 -0800 (PST) [thread overview]
Message-ID: <5e39a8b5.1c69fb81.8ed49.8655@mx.google.com> (raw)
next/master boot: 245 boots: 12 failed, 231 passed with 2 offline (next-20200204)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20200204/
Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20200204/
Tree: next
Branch: master
Git Describe: next-20200204
Git Commit: 03cd8b289266238f8122d11c2aa14763ca1e2971
Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 101 unique boards, 25 SoC families, 29 builds out of 200
Boot Regressions Detected:
arm:
davinci_all_defconfig:
gcc-8:
da850-lcdk:
lab-baylibre: new failure (last pass: next-20200203)
sunxi_defconfig:
gcc-8:
sun4i-a10-cubieboard:
lab-baylibre-seattle: new failure (last pass: next-20200203)
tegra_defconfig:
gcc-8:
tegra30-beaver:
lab-baylibre-seattle: failing since 1 day (last pass: next-20200131 - first fail: next-20200203)
arm64:
defconfig:
gcc-8:
apq8016-sbc:
lab-bjorn: failing since 4 days (last pass: next-20200130 - first fail: next-20200131)
meson-gxm-q200:
lab-baylibre: new failure (last pass: next-20200203)
Boot Failures Detected:
arm:
multi_v5_defconfig:
gcc-8:
da850-lcdk: 1 failed lab
qcom_defconfig:
gcc-8:
qcom-apq8064-cm-qs600: 1 failed lab
davinci_all_defconfig:
gcc-8:
da850-evm: 1 failed lab
da850-lcdk: 1 failed lab
dm365evm,legacy: 1 failed lab
multi_v7_defconfig:
gcc-8:
bcm2836-rpi-2-b: 1 failed lab
sun4i-a10-cubieboard: 1 failed lab
sunxi_defconfig:
gcc-8:
sun4i-a10-cubieboard: 1 failed lab
exynos_defconfig:
gcc-8:
exynos5422-odroidxu3: 1 failed lab
arm64:
defconfig:
gcc-8:
apq8016-sbc: 1 failed lab
meson-gxm-q200: 1 failed lab
msm8998-mtp: 1 failed lab
Offline Platforms:
arm:
multi_v7_defconfig:
gcc-8
tegra30-beaver: 1 offline lab
tegra_defconfig:
gcc-8
tegra30-beaver: 1 offline lab
---
For more info write to <info@kernelci.org>
reply other threads:[~2020-02-04 17:24 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=5e39a8b5.1c69fb81.8ed49.8655@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).