From: "kernelci.org bot" <bot@kernelci.org>
To: stable@vger.kernel.org
Subject: stable-rc/linux-4.14.y boot: 126 boots: 1 failed, 114 passed with 5 offline, 5 untried/unknown, 1 conflict (v4.14.178-27-g6d39cf919746)
Date: Mon, 04 May 2020 17:43:34 -0700 (PDT) [thread overview]
Message-ID: <5eb0b6b6.1c69fb81.3a91c.1336@mx.google.com> (raw)
stable-rc/linux-4.14.y boot: 126 boots: 1 failed, 114 passed with 5 offline, 5 untried/unknown, 1 conflict (v4.14.178-27-g6d39cf919746)
Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.14.y/kernel/v4.14.178-27-g6d39cf919746/
Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.14.y/kernel/v4.14.178-27-g6d39cf919746/
Tree: stable-rc
Branch: linux-4.14.y
Git Describe: v4.14.178-27-g6d39cf919746
Git Commit: 6d39cf91974673a74d6d976ecc107e43bb5c3eb4
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Tested: 72 unique boards, 20 SoC families, 17 builds out of 201
Boot Regressions Detected:
arm:
qcom_defconfig:
gcc-8:
qcom-apq8064-cm-qs600:
lab-baylibre-seattle: failing since 86 days (last pass: v4.14.169-92-gb4137330c582 - first fail: v4.14.170-62-gd6856e4a2c23)
versatile_defconfig:
gcc-8:
versatile-pb:
lab-collabora: new failure (last pass: v4.14.178)
Boot Failure Detected:
arm64:
defconfig:
gcc-8:
meson-gxbb-p200: 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
qcom_defconfig:
gcc-8
qcom-apq8064-cm-qs600: 1 offline lab
exynos_defconfig:
gcc-8
exynos5800-peach-pi: 1 offline lab
Conflicting Boot Failure Detected: (These likely are not failures as other labs are reporting PASS. Needs review.)
x86_64:
x86_64_defconfig:
qemu_x86_64:
lab-baylibre: PASS (gcc-8)
lab-collabora: FAIL (gcc-8)
---
For more info write to <info@kernelci.org>
reply other threads:[~2020-05-05 0:43 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=5eb0b6b6.1c69fb81.3a91c.1336@mx.google.com \
--to=bot@kernelci.org \
--cc=stable@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.