public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: "kernelci.org bot" <bot@kernelci.org>
To: cip-dev+int+1680+2922216858170285886@lists.cip-project.org,
	kernel-build-reports@lists.linaro.org,
	kernelci-results@groups.io
Subject: cip/linux-4.19.y-cip baseline-nfs: 54 runs, 2 regressions (v4.19.306-cip107)
Date: Sun, 18 Feb 2024 22:11:11 -0800 (PST)	[thread overview]
Message-ID: <65d2f0ff.170a0220.23e1b.a558@mx.google.com> (raw)

cip/linux-4.19.y-cip baseline-nfs: 54 runs, 2 regressions (v4.19.306-cip107)

Regressions Summary
-------------------

platform         | arch  | lab           | compiler | defconfig                  | regressions
-----------------+-------+---------------+----------+----------------------------+------------
rk3399-gru-kevin | arm64 | lab-collabora | gcc-10   | defconfig+arm64-chromebook | 2          

  Details:  https://kernelci.org/test/job/cip/branch/linux-4.19.y-cip/kernel/v4.19.306-cip107/plan/baseline-nfs/

  Test:     baseline-nfs
  Tree:     cip
  Branch:   linux-4.19.y-cip
  Describe: v4.19.306-cip107
  URL:      https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git
  SHA:      800dfc28d1a90b195d50f75fa7711d00cc1825bf 


Test Regressions
---------------- 


platform         | arch  | lab           | compiler | defconfig                  | regressions
-----------------+-------+---------------+----------+----------------------------+------------
rk3399-gru-kevin | arm64 | lab-collabora | gcc-10   | defconfig+arm64-chromebook | 2          

  Details:     https://kernelci.org/test/plan/id/65d2ea664a208a9eef637039

  Results:     77 PASS, 5 FAIL, 1 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/linux-4.19.y-cip/v4.19.306-cip107/arm64/defconfig+arm64-chromebook/gcc-10/lab-collabora/baseline-nfs-rk3399-gru-kevin.txt
  HTML log:    https://storage.kernelci.org//cip/linux-4.19.y-cip/v4.19.306-cip107/arm64/defconfig+arm64-chromebook/gcc-10/lab-collabora/baseline-nfs-rk3399-gru-kevin.html
  Rootfs:      http://storage.kernelci.org/images/rootfs/debian/bullseye/20230623.0/arm64/initrd.cpio.gz 


  * baseline-nfs.bootrr.rockchip-usb2phy1-probed: https://kernelci.org/test/case/id/65d2ea664a208a9eef637043
        failing since 333 days (last pass: v4.19.276-cip93, first fail: v4.19.277-cip94)

    2024-02-19T05:42:52.140011  /lava-12799815/1/../bin/lava-test-case

    2024-02-19T05:42:52.160659  <8>[   39.469741] <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=rockchip-usb2phy1-probed RESULT=fail>
   

  * baseline-nfs.bootrr.rockchip-usb2phy0-probed: https://kernelci.org/test/case/id/65d2ea664a208a9eef637044
        failing since 333 days (last pass: v4.19.276-cip93, first fail: v4.19.277-cip94)

    2024-02-19T05:42:51.089910  /lava-12799815/1/../bin/lava-test-case

    2024-02-19T05:42:51.110285  <8>[   38.419345] <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=rockchip-usb2phy0-probed RESULT=fail>
   
  


                 reply	other threads:[~2024-02-19  6:11 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=65d2f0ff.170a0220.23e1b.a558@mx.google.com \
    --to=bot@kernelci.org \
    --cc=cip-dev+int+1680+2922216858170285886@lists.cip-project.org \
    --cc=kernel-build-reports@lists.linaro.org \
    --cc=kernelci-results@groups.io \
    /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