From: "kernelci.org bot" <bot@kernelci.org>
To: linux-gpio@vger.kernel.org, fellows@kernelci.org
Subject: linusw/for-next boot: 37 boots: 2 failed, 35 passed (v5.3-rc1-10-gd2a561ae1961)
Date: Mon, 29 Jul 2019 20:19:17 -0700 (PDT) [thread overview]
Message-ID: <5d3fb735.1c69fb81.39b2e.863c@mx.google.com> (raw)
linusw/for-next boot: 37 boots: 2 failed, 35 passed (v5.3-rc1-10-gd2a561ae1961)
Full Boot Summary: https://kernelci.org/boot/all/job/linusw/branch/for-next/kernel/v5.3-rc1-10-gd2a561ae1961/
Full Build Summary: https://kernelci.org/build/linusw/branch/for-next/kernel/v5.3-rc1-10-gd2a561ae1961/
Tree: linusw
Branch: for-next
Git Describe: v5.3-rc1-10-gd2a561ae1961
Git Commit: d2a561ae19613c14bfbc437bc9dbdb2c9d1d1b95
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git/
Tested: 27 unique boards, 13 SoC families, 3 builds out of 6
Boot Regressions Detected:
arm64:
defconfig:
gcc-8:
apq8016-sbc:
lab-mhart: new failure (last pass: v5.2-10813-g88785b7fa74a)
meson-gxm-khadas-vim2:
lab-baylibre: new failure (last pass: v5.2-rc2-89-g9b3b623804a6)
Boot Failures Detected:
arm64:
defconfig:
gcc-8:
apq8016-sbc: 1 failed lab
meson-gxm-khadas-vim2: 1 failed lab
---
For more info write to <info@kernelci.org>
reply other threads:[~2019-07-30 3:19 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=5d3fb735.1c69fb81.39b2e.863c@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