From: "kernelci.org bot" <bot@kernelci.org>
To: linux-next@vger.kernel.org
Subject: next/master boot: 255 boots: 10 failed, 238 passed with 6 offline, 1 untried/unknown (next-20200203)
Date: Mon, 03 Feb 2020 00:34:05 -0800 (PST) [thread overview]
Message-ID: <5e37dafd.1c69fb81.4be02.f324@mx.google.com> (raw)
next/master boot: 255 boots: 10 failed, 238 passed with 6 offline, 1 untried/unknown (next-20200203)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20200203/
Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20200203/
Tree: next
Branch: master
Git Describe: next-20200203
Git Commit: cee5a42837d4a6c4189f06f7bf355b97a24c3c93
Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 101 unique boards, 25 SoC families, 27 builds out of 202
Boot Regressions Detected:
arm:
multi_v7_defconfig:
gcc-8:
mt7629-rfb:
lab-baylibre-seattle: new failure (last pass: next-20200130)
tegra_defconfig:
gcc-8:
tegra30-beaver:
lab-baylibre-seattle: new failure (last pass: next-20200131)
versatile_defconfig:
gcc-8:
versatile-pb:
lab-collabora: new failure (last pass: next-20200130)
arm64:
defconfig:
gcc-8:
apq8016-sbc:
lab-bjorn: failing since 2 days (last pass: next-20200130 - first fail: next-20200131)
bcm2837-rpi-3-b:
lab-baylibre: new failure (last pass: next-20200131)
meson-axg-s400:
lab-baylibre-seattle: new failure (last pass: next-20200131)
sun50i-a64-bananapi-m64:
lab-clabbe: new failure (last pass: next-20200131)
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8:
meson-axg-s400:
lab-baylibre-seattle: new failure (last pass: next-20200131)
defconfig+CONFIG_RANDOMIZE_BASE=y:
gcc-8:
meson-axg-s400:
lab-baylibre-seattle: new failure (last pass: next-20200131)
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
dm365evm,legacy: 1 failed lab
sama5_defconfig:
gcc-8:
at91-sama5d4_xplained: 1 failed lab
multi_v7_defconfig:
gcc-8:
bcm2836-rpi-2-b: 1 failed lab
exynos_defconfig:
gcc-8:
exynos5422-odroidxu3: 1 failed lab
arm64:
defconfig:
gcc-8:
apq8016-sbc: 1 failed lab
bcm2837-rpi-3-b: 1 failed lab
msm8998-mtp: 1 failed lab
Offline Platforms:
arm:
multi_v7_defconfig:
gcc-8
mt7629-rfb: 1 offline lab
tegra30-beaver: 1 offline lab
tegra_defconfig:
gcc-8
tegra30-beaver: 1 offline lab
arm64:
defconfig+CONFIG_RANDOMIZE_BASE=y:
gcc-8
meson-axg-s400: 1 offline lab
defconfig:
gcc-8
meson-axg-s400: 1 offline lab
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8
meson-axg-s400: 1 offline lab
---
For more info write to <info@kernelci.org>
reply other threads:[~2020-02-03 8:34 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=5e37dafd.1c69fb81.4be02.f324@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.