From: "kernelci.org bot" <bot@kernelci.org>
To: linux-renesas-soc@vger.kernel.org, kernelci-results@groups.io
Subject: renesas/next ltp-ipc: 4 runs, 1 regressions (renesas-next-2024-06-27-v6.10-rc1)
Date: Thu, 27 Jun 2024 12:55:25 -0700 (PDT) [thread overview]
Message-ID: <667dc3ad.170a0220.64d63.0f03@mx.google.com> (raw)
renesas/next ltp-ipc: 4 runs, 1 regressions (renesas-next-2024-06-27-v6.10-rc1)
Regressions Summary
-------------------
platform | arch | lab | compiler | defconfig | regressions
------------------+-------+-------------+----------+-----------+------------
qemu_smp8_riscv64 | riscv | lab-broonie | gcc-10 | defconfig | 1
Details: https://kernelci.org/test/job/renesas/branch/next/kernel/renesas-next-2024-06-27-v6.10-rc1/plan/ltp-ipc/
Test: ltp-ipc
Tree: renesas
Branch: next
Describe: renesas-next-2024-06-27-v6.10-rc1
URL: https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git
SHA: 91aa9e4e18c70bc2160b63e403932a83226dfc67
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/667db71362adc88e8a7e7091
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//renesas/next/renesas-next-2024-06-27-v6.10-rc1/riscv/defconfig/gcc-10/lab-broonie/ltp-ipc-qemu_smp8_riscv64.txt
HTML log: https://storage.kernelci.org//renesas/next/renesas-next-2024-06-27-v6.10-rc1/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/667db71362adc88e8a7e7092
new failure (last pass: renesas-next-2024-06-25-v6.10-rc1)
reply other threads:[~2024-06-27 19:55 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=667dc3ad.170a0220.64d63.0f03@mx.google.com \
--to=bot@kernelci.org \
--cc=kernelci-results@groups.io \
--cc=linux-renesas-soc@vger.kernel.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 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.