From: "kernelci.org bot" <bot@kernelci.org>
To: cip-dev+int+1680+2922216858170285886@lists.cip-project.org
Subject: cip-gitlab/ci/pavel/linux-test baseline-nfs: 14 runs, 3 regressions (v5.10.131-cip13)
Date: Tue, 02 Aug 2022 13:30:36 -0700 (PDT) [thread overview]
Message-ID: <62e9896c.170a0220.7916f.0447@mx.google.com> (raw)
cip-gitlab/ci/pavel/linux-test baseline-nfs: 14 runs, 3 regressions (v5.10.131-cip13)
Regressions Summary
-------------------
platform | arch | lab | compiler | defconfig | regressions
-----------------+-------+---------------+----------+----------------------------+------------
rk3399-gru-kevin | arm64 | lab-collabora | gcc-10 | defconfig+arm64-chromebook | 3
Details: https://kernelci.org/test/job/cip-gitlab/branch/ci%2Fpavel%2Flinux-test/kernel/v5.10.131-cip13/plan/baseline-nfs/
Test: baseline-nfs
Tree: cip-gitlab
Branch: ci/pavel/linux-test
Describe: v5.10.131-cip13
URL: https://gitlab.com/cip-project/cip-kernel/linux-cip.git
SHA: e217bcd84090afd29c7a9ab120fb3c8ff8844478
Test Regressions
----------------
platform | arch | lab | compiler | defconfig | regressions
-----------------+-------+---------------+----------+----------------------------+------------
rk3399-gru-kevin | arm64 | lab-collabora | gcc-10 | defconfig+arm64-chromebook | 3
Details: https://kernelci.org/test/plan/id/62e97de3203c33deafdaf0dd
Results: 84 PASS, 4 FAIL, 0 SKIP
Full config: defconfig+arm64-chromebook
Compiler: gcc-10 (aarch64-linux-gnu-gcc (Debian 10.2.1-6) 10.2.1 20210110)
Plain log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v5.10.131-cip13/arm64/defconfig+arm64-chromebook/gcc-10/lab-collabora/baseline-nfs-rk3399-gru-kevin.txt
HTML log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v5.10.131-cip13/arm64/defconfig+arm64-chromebook/gcc-10/lab-collabora/baseline-nfs-rk3399-gru-kevin.html
Rootfs: http://storage.kernelci.org/images/rootfs/debian/bullseye/20220718.0/arm64/initrd.cpio.gz
* baseline-nfs.bootrr.cros-ec-sensors-gyro0-probed: https://kernelci.org/test/case/id/62e97de4203c33deafdaf120
failing since 84 days (last pass: v4.19.233-516-ge5e741fbfc87, first fail: v5.10.109-cip5-384-g722204542e8a)
2022-08-02T19:41:04.916667 <8>[ 93.188208] <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=cros-ec-sensors-accel1-probed RESULT=fail>
2022-08-02T19:41:05.951876 /lava-6951001/1/../bin/lava-test-case
2022-08-02T19:41:05.983316 <8>[ 94.255469] <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=cros-ec-sensors-gyro0-probed RESULT=fail>
* baseline-nfs.bootrr.cros-ec-sensors-accel1-probed: https://kernelci.org/test/case/id/62e97de4203c33deafdaf121
failing since 84 days (last pass: v4.19.233-516-ge5e741fbfc87, first fail: v5.10.109-cip5-384-g722204542e8a)
2022-08-02T19:41:04.885961 /lava-6951001/1/../bin/lava-test-case
* baseline-nfs.bootrr.cros-ec-sensors-accel0-probed: https://kernelci.org/test/case/id/62e97de4203c33deafdaf122
failing since 84 days (last pass: v4.19.233-516-ge5e741fbfc87, first fail: v5.10.109-cip5-384-g722204542e8a)
2022-08-02T19:41:02.777507 <8>[ 91.049143] <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=cros-ec-sensors-driver-present RESULT=pass>
2022-08-02T19:41:03.811008 /lava-6951001/1/../bin/lava-test-case
2022-08-02T19:41:03.844478 <8>[ 92.116469] <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=cros-ec-sensors-accel0-probed RESULT=fail>
reply other threads:[~2022-08-02 20:30 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=62e9896c.170a0220.7916f.0447@mx.google.com \
--to=bot@kernelci.org \
--cc=cip-dev+int+1680+2922216858170285886@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