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-5.10.y-cip ltp-ipc: 4 runs, 2 regressions (v5.10.191-cip38-29-g9e1aa2001db8)
Date: Wed, 13 Sep 2023 10:39:53 -0700 (PDT) [thread overview]
Message-ID: <6501f3e9.a70a0220.26561.bf36@mx.google.com> (raw)
cip/linux-5.10.y-cip ltp-ipc: 4 runs, 2 regressions (v5.10.191-cip38-29-g9e1aa2001db8)
Regressions Summary
-------------------
platform | arch | lab | compiler | defconfig | regressions
------------------+-------+---------------+----------+-----------+------------
qemu_smp8_riscv64 | riscv | lab-broonie | gcc-10 | defconfig | 1
qemu_smp8_riscv64 | riscv | lab-collabora | gcc-10 | defconfig | 1
Details: https://kernelci.org/test/job/cip/branch/linux-5.10.y-cip/kernel/v5.10.191-cip38-29-g9e1aa2001db8/plan/ltp-ipc/
Test: ltp-ipc
Tree: cip
Branch: linux-5.10.y-cip
Describe: v5.10.191-cip38-29-g9e1aa2001db8
URL: https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git
SHA: 9e1aa2001db862da32812062860b8756cbc8890a
Test suite revisions:
ltp-tests
URL: https://github.com/linux-test-project/ltp.git
SHA: 3f0b2176930cf15a26597e28abf4356050136bbe
Test Regressions
----------------
platform | arch | lab | compiler | defconfig | regressions
------------------+-------+---------------+----------+-----------+------------
qemu_smp8_riscv64 | riscv | lab-broonie | gcc-10 | defconfig | 1
Details: https://kernelci.org/test/plan/id/6501e391bf1499c7ef8a0a57
Results: 0 PASS, 1 FAIL, 0 SKIP
Full config: defconfig
Compiler: gcc-10 (riscv64-linux-gnu-gcc (Debian 10.2.1-6) 10.2.1 20210110)
Plain log: https://storage.kernelci.org//cip/linux-5.10.y-cip/v5.10.191-cip38-29-g9e1aa2001db8/riscv/defconfig/gcc-10/lab-broonie/ltp-ipc-qemu_smp8_riscv64.txt
HTML log: https://storage.kernelci.org//cip/linux-5.10.y-cip/v5.10.191-cip38-29-g9e1aa2001db8/riscv/defconfig/gcc-10/lab-broonie/ltp-ipc-qemu_smp8_riscv64.html
Rootfs: http://storage.kernelci.org/images/rootfs/debian/sid-ltp/20230623.0/riscv64/rootfs.cpio.gz
* ltp-ipc.login: https://kernelci.org/test/case/id/6501e391bf1499c7ef8a0a58
new failure (last pass: v5.10.191-cip38-17-g8dad6b499cfe5)
platform | arch | lab | compiler | defconfig | regressions
------------------+-------+---------------+----------+-----------+------------
qemu_smp8_riscv64 | riscv | lab-collabora | gcc-10 | defconfig | 1
Details: https://kernelci.org/test/plan/id/6501e35f21ad6de7e68a0a9b
Results: 0 PASS, 1 FAIL, 0 SKIP
Full config: defconfig
Compiler: gcc-10 (riscv64-linux-gnu-gcc (Debian 10.2.1-6) 10.2.1 20210110)
Plain log: https://storage.kernelci.org//cip/linux-5.10.y-cip/v5.10.191-cip38-29-g9e1aa2001db8/riscv/defconfig/gcc-10/lab-collabora/ltp-ipc-qemu_smp8_riscv64.txt
HTML log: https://storage.kernelci.org//cip/linux-5.10.y-cip/v5.10.191-cip38-29-g9e1aa2001db8/riscv/defconfig/gcc-10/lab-collabora/ltp-ipc-qemu_smp8_riscv64.html
Rootfs: http://storage.kernelci.org/images/rootfs/debian/sid-ltp/20230623.0/riscv64/rootfs.cpio.gz
* ltp-ipc.login: https://kernelci.org/test/case/id/6501e35f21ad6de7e68a0a9c
new failure (last pass: v5.10.191-cip38-17-g8dad6b499cfe5)
reply other threads:[~2023-09-13 17:40 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=6501f3e9.a70a0220.26561.bf36@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