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-cip-nfs: 2 runs, 2 regressions (v4.4-st5-312-g3a12bf5207d81)
Date: Wed, 15 Jun 2022 02:04:54 -0700 (PDT) [thread overview]
Message-ID: <62a9a0b6.1c69fb81.3e3d6.b2e1@mx.google.com> (raw)
cip-gitlab/ci/pavel/linux-test baseline-cip-nfs: 2 runs, 2 regressions (v4.4-st5-312-g3a12bf5207d81)
Regressions Summary
-------------------
platform | arch | lab | compiler | defconfig | regressions
-----------------+------+-------------+----------+--------------------+------------
beaglebone-black | arm | lab-broonie | gcc-10 | multi_v7_defconfig | 1
beaglebone-black | arm | lab-cip | gcc-10 | multi_v7_defconfig | 1
Details: https://kernelci.org/test/job/cip-gitlab/branch/ci%2Fpavel%2Flinux-test/kernel/v4.4-st5-312-g3a12bf5207d81/plan/baseline-cip-nfs/
Test: baseline-cip-nfs
Tree: cip-gitlab
Branch: ci/pavel/linux-test
Describe: v4.4-st5-312-g3a12bf5207d81
URL: https://gitlab.com/cip-project/cip-kernel/linux-cip.git
SHA: 3a12bf5207d810922b696a4c99c88e2841af6212
Test Regressions
----------------
platform | arch | lab | compiler | defconfig | regressions
-----------------+------+-------------+----------+--------------------+------------
beaglebone-black | arm | lab-broonie | gcc-10 | multi_v7_defconfig | 1
Details: https://kernelci.org/test/plan/id/62a758df7fd51aab4da39bd2
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-gitlab/ci-pavel-linux-test/v4.4-st5-312-g3a12bf5207d81/arm/multi_v7_defconfig/gcc-10/lab-broonie/baseline-cip-nfs-beaglebone-black.txt
HTML log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st5-312-g3a12bf5207d81/arm/multi_v7_defconfig/gcc-10/lab-broonie/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/62a758df7fd51aab4da39bd3
failing since 33 days (last pass: v5.10.109-cip5-384-g722204542e8a, first fail: v4.4-st5-260-gb0fe64f485ff)
platform | arch | lab | compiler | defconfig | regressions
-----------------+------+-------------+----------+--------------------+------------
beaglebone-black | arm | lab-cip | gcc-10 | multi_v7_defconfig | 1
Details: https://kernelci.org/test/plan/id/62a7566aba9e217037a39be5
Results: 3 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-gitlab/ci-pavel-linux-test/v4.4-st5-312-g3a12bf5207d81/arm/multi_v7_defconfig/gcc-10/lab-cip/baseline-cip-nfs-beaglebone-black.txt
HTML log: https://storage.kernelci.org//cip-gitlab/ci-pavel-linux-test/v4.4-st5-312-g3a12bf5207d81/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.dmesg.crit: https://kernelci.org/test/case/id/62a7566aba9e217037a39be8
failing since 15 days (last pass: v5.10.112-cip6, first fail: v4.4-st5-297-gc0d53c2a5c03d)
1 lines
2022-06-13T15:23:04.705760 / #
2022-06-13T15:23:04.713207
2022-06-13T15:23:09.746029 / # export NFS_ROOTFS='/var/lib/lava/dispatcher/tmp/697172/extract-nfsrootfs-1zssbssy'
2022-06-13T15:23:09.756852 export NFS_ROOTFS='/var/lib/lava/dispatcher/tmp/697172/extract-nfsrootfs-</lib/lava/dispatcher/tmp/697172/extract-nfsrootfs-1 zssbssy'
2022-06-13T15:23:11.817894 / # export NFS_SERVER_IP='172.16.3.3'
2022-06-13T15:23:11.828631 export NFS_SERVER_IP='172.16.3.3'
2022-06-13T15:23:11.940192 / # #
2022-06-13T15:23:11.947294 #
2022-06-13T15:23:12.059637 / # export SHELL=/bin/sh
2022-06-13T15:23:12.065730 export SHELL=/bin/sh
... (13 line(s) more)
reply other threads:[~2022-06-15 9:05 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=62a9a0b6.1c69fb81.3e3d6.b2e1@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