From: "kernelci.org bot" <bot@kernelci.org>
To: linux-gpio@vger.kernel.org, fellows@kernelci.org
Subject: linusw/for-next baseline: 123 runs, 1 regressions (v5.8-rc5-76-g60e149cc2965)
Date: Thu, 23 Jul 2020 19:02:26 -0700 (PDT) [thread overview]
Message-ID: <5f1a4132.1c69fb81.6a40b.af2e@mx.google.com> (raw)
linusw/for-next baseline: 123 runs, 1 regressions (v5.8-rc5-76-g60e149cc2965)
Regressions Summary
-------------------
platform | arch | lab | compiler | defconfig | results
----------------+-------+--------------+----------+-----------+--------
bcm2837-rpi-3-b | arm64 | lab-baylibre | gcc-8 | defconfig | 4/5
Details: https://kernelci.org/test/job/linusw/branch/for-next/kernel/v5.8-rc5-76-g60e149cc2965/plan/baseline/
Test: baseline
Tree: linusw
Branch: for-next
Describe: v5.8-rc5-76-g60e149cc2965
URL: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git/
SHA: 60e149cc2965b77a0d1c74c04bfd1e156b8fb083
Test Regressions
----------------
platform | arch | lab | compiler | defconfig | results
----------------+-------+--------------+----------+-----------+--------
bcm2837-rpi-3-b | arm64 | lab-baylibre | gcc-8 | defconfig | 4/5
Details: https://kernelci.org/test/plan/id/5f1a2e400aaf81587d85bb51
Results: 4 PASS, 1 FAIL, 0 SKIP
Full config: defconfig
Compiler: gcc-8 (aarch64-linux-gnu-gcc (Debian 8.3.0-2) 8.3.0)
Plain log: https://storage.kernelci.org//linusw/for-next/v5.8-rc5-76-g60e149cc2965/arm64/defconfig/gcc-8/lab-baylibre/baseline-bcm2837-rpi-3-b.txt
HTML log: https://storage.kernelci.org//linusw/for-next/v5.8-rc5-76-g60e149cc2965/arm64/defconfig/gcc-8/lab-baylibre/baseline-bcm2837-rpi-3-b.html
Rootfs: http://storage.kernelci.org/images/rootfs/buildroot/kci-2020.05/arm64/baseline/rootfs.cpio.gz
* baseline.dmesg.crit: https://kernelci.org/test/case/id/5f1a2e400aaf81587d85bb54
failing since 7 days (last pass: gpio-v5.8-2-58-g1752911c6d10, first fail: v5.8-rc5-68-geb211a587e18)
2 lines
reply other threads:[~2020-07-24 2:02 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=5f1a4132.1c69fb81.6a40b.af2e@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).