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-6.1.y-cip baseline-nfs: 22 runs, 2 regressions (v6.1.52-cip5)
Date: Fri, 08 Sep 2023 07:03:05 -0700 (PDT) [thread overview]
Message-ID: <64fb2999.170a0220.44ed2.34ae@mx.google.com> (raw)
cip/linux-6.1.y-cip baseline-nfs: 22 runs, 2 regressions (v6.1.52-cip5)
Regressions Summary
-------------------
platform | arch | lab | compiler | defconfig | regressions
-----------------+-------+---------------+----------+----------------------------+------------
imx6q-udoo | arm | lab-broonie | gcc-10 | imx_v6_v7_defconfig | 1
rk3399-gru-kevin | arm64 | lab-collabora | gcc-10 | defconfig+arm64-chromebook | 1
Details: https://kernelci.org/test/job/cip/branch/linux-6.1.y-cip/kernel/v6.1.52-cip5/plan/baseline-nfs/
Test: baseline-nfs
Tree: cip
Branch: linux-6.1.y-cip
Describe: v6.1.52-cip5
URL: https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git
SHA: 98ee1708ccc7301dbbfaafec75350f88527046a1
Test Regressions
----------------
platform | arch | lab | compiler | defconfig | regressions
-----------------+-------+---------------+----------+----------------------------+------------
imx6q-udoo | arm | lab-broonie | gcc-10 | imx_v6_v7_defconfig | 1
Details: https://kernelci.org/test/plan/id/64fb21d5f801f9d97e286d88
Results: 0 PASS, 1 FAIL, 0 SKIP
Full config: imx_v6_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-6.1.y-cip/v6.1.52-cip5/arm/imx_v6_v7_defconfig/gcc-10/lab-broonie/baseline-nfs-imx6q-udoo.txt
HTML log: https://storage.kernelci.org//cip/linux-6.1.y-cip/v6.1.52-cip5/arm/imx_v6_v7_defconfig/gcc-10/lab-broonie/baseline-nfs-imx6q-udoo.html
Rootfs: http://storage.kernelci.org/images/rootfs/debian/bullseye/20230623.0/armhf/initrd.cpio.gz
* baseline-nfs.login: https://kernelci.org/test/case/id/64fb21d5f801f9d97e286d89
failing since 49 days (last pass: v6.1.31-65-ge66be31505fa, first fail: v6.1.38-cip1-10-gf4eb42f19246)
platform | arch | lab | compiler | defconfig | regressions
-----------------+-------+---------------+----------+----------------------------+------------
rk3399-gru-kevin | arm64 | lab-collabora | gcc-10 | defconfig+arm64-chromebook | 1
Details: https://kernelci.org/test/plan/id/64fb25776f5516f0b7286d74
Results: 0 PASS, 1 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/linux-6.1.y-cip/v6.1.52-cip5/arm64/defconfig+arm64-chromebook/gcc-10/lab-collabora/baseline-nfs-rk3399-gru-kevin.txt
HTML log: https://storage.kernelci.org//cip/linux-6.1.y-cip/v6.1.52-cip5/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.login: https://kernelci.org/test/case/id/64fb25776f5516f0b7286d75
new failure (last pass: v6.1.46-cip4-14-g09ffd7fb38ff)
reply other threads:[~2023-09-08 14:03 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=64fb2999.170a0220.44ed2.34ae@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.