From: "kernelci.org bot" <bot@kernelci.org>
To: Cipproject+Cip-Dev via Email Integration <cip-dev@lists.cip-project.org>
Subject: cip/linux-4.19.y-cip baseline-cip-nfs: 5 runs, 1 regressions (v4.19.231-cip68) #kernelci
Date: Tue, 01 Mar 2022 02:56:25 -0800 (PST) [thread overview]
Message-ID: <621dfbd9.1c69fb81.a4925.9998@mx.google.com> (raw)
cip/linux-4.19.y-cip baseline-cip-nfs: 5 runs, 1 regressions (v4.19.231-cip68)
Regressions Summary
-------------------
platform | arch | lab | compiler | defconfig | regressions
-----------------+------+---------+----------+--------------------+------------
beaglebone-black | arm | lab-cip | gcc-10 | multi_v7_defconfig | 1
Details: https://kernelci.org/test/job/cip/branch/linux-4.19.y-cip/kernel/v4.19.231-cip68/plan/baseline-cip-nfs/
Test: baseline-cip-nfs
Tree: cip
Branch: linux-4.19.y-cip
Describe: v4.19.231-cip68
URL: https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git
SHA: c7477548dcf8c653b00e361f7a724f0b94e7d372
Test Regressions
----------------
platform | arch | lab | compiler | defconfig | regressions
-----------------+------+---------+----------+--------------------+------------
beaglebone-black | arm | lab-cip | gcc-10 | multi_v7_defconfig | 1
Details: https://kernelci.org/test/plan/id/621df03605c05dbfb7c62987
Results: 0 PASS, 1 FAIL, 0 SKIP
Full config: multi_v7_defconfig
Compiler: gcc-10 (arm-linux-gnueabihf-gcc (Debian 10.2.1-6) 10.2.1 20210110)
Plain log: https://storage.kernelci.org//cip/linux-4.19.y-cip/v4.19.231-cip68/arm/multi_v7_defconfig/gcc-10/lab-cip/baseline-cip-nfs-beaglebone-black.txt
HTML log: https://storage.kernelci.org//cip/linux-4.19.y-cip/v4.19.231-cip68/arm/multi_v7_defconfig/gcc-10/lab-cip/baseline-cip-nfs-beaglebone-black.html
Rootfs: https://storage.kernelci.org/images/rootfs/cip/20211105/qemu-arm/cip-core-image-kernelci-cip-core-buster-qemu-arm-initrd.img.gz
* baseline-cip-nfs.login: https://kernelci.org/test/case/id/621df03605c05dbfb7c62988
new failure (last pass: v4.19.229-cip67)
reply other threads:[~2022-03-01 10:56 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=621dfbd9.1c69fb81.a4925.9998@mx.google.com \
--to=bot@kernelci.org \
--cc=cip-dev@lists.cip-project.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