From: "kernelci.org bot" <bot@kernelci.org>
To: linux-gpio@vger.kernel.org, fellows@kernelci.org
Subject: linusw/for-next boot: 20 boots: 2 failed, 18 passed (v5.7-rc1)
Date: Wed, 15 Apr 2020 21:57:48 -0700 (PDT) [thread overview]
Message-ID: <5e97e5cc.1c69fb81.429a7.3cfe@mx.google.com> (raw)
linusw/for-next boot: 20 boots: 2 failed, 18 passed (v5.7-rc1)
Full Boot Summary: https://kernelci.org/boot/all/job/linusw/branch/for-next/kernel/v5.7-rc1/
Full Build Summary: https://kernelci.org/build/linusw/branch/for-next/kernel/v5.7-rc1/
Tree: linusw
Branch: for-next
Git Describe: v5.7-rc1
Git Commit: 8f3d9f354286745c751374f5f1fcafee6b3f3136
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git/
Tested: 20 unique boards, 9 SoC families, 3 builds out of 6
Boot Regressions Detected:
arm:
multi_v7_defconfig:
gcc-8:
bcm2836-rpi-2-b:
lab-collabora: failing since 64 days (last pass: gpio-v5.5-4-45-gd18fddff061d - first fail: v5.6-rc1-12-g612e35e76ec8)
exynos5422-odroidxu3:
lab-collabora: new failure (last pass: v5.6-rc7-64-g4ed7d7dd4890)
Boot Failures Detected:
arm:
multi_v7_defconfig:
gcc-8:
bcm2836-rpi-2-b: 1 failed lab
exynos5422-odroidxu3: 1 failed lab
---
For more info write to <info@kernelci.org>
reply other threads:[~2020-04-16 4:57 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=5e97e5cc.1c69fb81.429a7.3cfe@mx.google.com \
--to=bot@kernelci.org \
--cc=fellows@kernelci.org \
--cc=linux-gpio@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).