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
Subject: cip-gitlab/ci/iwamatsu/linux-4.19.y-cip-rc baseline-nfs: 37 runs, 1 regressions (v4.19.304-cip106-27-gf3e967c370d44)
Date: Mon, 15 Jan 2024 20:15:01 -0800 (PST)	[thread overview]
Message-ID: <65a602c5.170a0220.2e6c3.b32c@mx.google.com> (raw)

cip-gitlab/ci/iwamatsu/linux-4.19.y-cip-rc baseline-nfs: 37 runs, 1 regressions (v4.19.304-cip106-27-gf3e967c370d44)

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

platform      | arch | lab         | compiler | defconfig          | regressions
--------------+------+-------------+----------+--------------------+------------
at91sam9g20ek | arm  | lab-broonie | gcc-10   | multi_v5_defconfig | 1          

  Details:  https://kernelci.org/test/job/cip-gitlab/branch/ci%2Fiwamatsu%2Flinux-4.19.y-cip-rc/kernel/v4.19.304-cip106-27-gf3e967c370d44/plan/baseline-nfs/

  Test:     baseline-nfs
  Tree:     cip-gitlab
  Branch:   ci/iwamatsu/linux-4.19.y-cip-rc
  Describe: v4.19.304-cip106-27-gf3e967c370d44
  URL:      https://gitlab.com/cip-project/cip-kernel/linux-cip.git
  SHA:      f3e967c370d44f37d5b1b2cc02e9898573c4a4ee 


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


platform      | arch | lab         | compiler | defconfig          | regressions
--------------+------+-------------+----------+--------------------+------------
at91sam9g20ek | arm  | lab-broonie | gcc-10   | multi_v5_defconfig | 1          

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

  Results:     42 PASS, 9 FAIL, 1 SKIP
  Full config: multi_v5_defconfig
  Compiler:    gcc-10 (arm-linux-gnueabihf-gcc (Debian 10.2.1-6) 10.2.1 20210110)
  Plain log:   https://storage.kernelci.org//cip-gitlab/ci-iwamatsu-linux-4.19.y-cip-rc/v4.19.304-cip106-27-gf3e967c370d44/arm/multi_v5_defconfig/gcc-10/lab-broonie/baseline-nfs-at91sam9g20ek.txt
  HTML log:    https://storage.kernelci.org//cip-gitlab/ci-iwamatsu-linux-4.19.y-cip-rc/v4.19.304-cip106-27-gf3e967c370d44/arm/multi_v5_defconfig/gcc-10/lab-broonie/baseline-nfs-at91sam9g20ek.html
  Rootfs:      http://storage.kernelci.org/images/rootfs/debian/bullseye/20230623.0/armel/initrd.cpio.gz 


  * baseline-nfs.bootrr.deferred-probe-empty: https://kernelci.org/test/case/id/65a5fd5ce9837a745f52a429
        failing since 97 days (last pass: v4.19.284-cip99-114-g02e97826987bf, first fail: v4.19.295-cip103-95-ge42cfc8bb88b7)

    2024-01-16T03:51:09.391403  + set +x<8><LAVA_SIGNAL_ENDRUN 0_dmesg 461970_1.6.2.4.1>
    2024-01-16T03:51:09.508378  #
    2024-01-16T03:51:09.610422  / # #export SHELL=/bin/sh
    2024-01-16T03:51:09.611206  
    2024-01-16T03:51:09.713055  / # export SHELL=/bin/sh. /lava-461970/environment
    2024-01-16T03:51:09.713812  
    2024-01-16T03:51:09.815800  / # . /lava-461970/environment/lava-461970/bin/lava-test-runner /lava-461970/1
    2024-01-16T03:51:09.817100  
    2024-01-16T03:51:09.820578  / # /lava-461970/bin/lava-test-runner /lava-461970/1
    2024-01-16T03:51:10.174848  + export TESTRUN_ID=1_bootrr 
    ... (11 line(s) more)  
  


                 reply	other threads:[~2024-01-16  4:15 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=65a602c5.170a0220.2e6c3.b32c@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