From: "kernelci.org bot" <bot@kernelci.org>
To: linux-renesas-soc@vger.kernel.org, kernelci-results@groups.io
Subject: renesas/master ltp-ipc: 23 runs, 2 regressions (renesas-devel-2022-11-17-v6.1-rc5)
Date: Thu, 17 Nov 2022 15:29:18 -0800 (PST) [thread overview]
Message-ID: <6376c3ce.630a0220.3237d.2b31@mx.google.com> (raw)
renesas/master ltp-ipc: 23 runs, 2 regressions (renesas-devel-2022-11-17-v6.1-rc5)
Regressions Summary
-------------------
platform | arch | lab | compiler | defconfig | regressions
-----------------+-------+---------------+----------+----------------------------+------------
beaglebone-black | arm | lab-cip | gcc-10 | multi_v7_defconfig+ima | 1
mt8173-elm-hana | arm64 | lab-collabora | gcc-10 | defconfig+arm64-chromebook | 1
Details: https://kernelci.org/test/job/renesas/branch/master/kernel/renesas-devel-2022-11-17-v6.1-rc5/plan/ltp-ipc/
Test: ltp-ipc
Tree: renesas
Branch: master
Describe: renesas-devel-2022-11-17-v6.1-rc5
URL: https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git
SHA: 882ccb9771f9e9985a9ada17c5e35b4863258378
Test suite revisions:
ltp-tests
URL: https://github.com/linux-test-project/ltp.git
SHA: a15eb3cdfa3556203167572e15754f1f59ba26bf
Test Regressions
----------------
platform | arch | lab | compiler | defconfig | regressions
-----------------+-------+---------------+----------+----------------------------+------------
beaglebone-black | arm | lab-cip | gcc-10 | multi_v7_defconfig+ima | 1
Details: https://kernelci.org/test/plan/id/6376aa7366389451082abd26
Results: 0 PASS, 1 FAIL, 0 SKIP
Full config: multi_v7_defconfig+ima
Compiler: gcc-10 (arm-linux-gnueabihf-gcc (Debian 10.2.1-6) 10.2.1 20210110)
Plain log: https://storage.kernelci.org//renesas/master/renesas-devel-2022-11-17-v6.1-rc5/arm/multi_v7_defconfig+ima/gcc-10/lab-cip/ltp-ipc-beaglebone-black.txt
HTML log: https://storage.kernelci.org//renesas/master/renesas-devel-2022-11-17-v6.1-rc5/arm/multi_v7_defconfig+ima/gcc-10/lab-cip/ltp-ipc-beaglebone-black.html
Rootfs: http://storage.kernelci.org/images/rootfs/debian/bullseye-ltp/20221107.1/armhf/initrd.cpio.gz
* ltp-ipc.login: https://kernelci.org/test/case/id/6376aa7366389451082abd27
new failure (last pass: renesas-devel-2022-11-10-v6.1-rc4)
platform | arch | lab | compiler | defconfig | regressions
-----------------+-------+---------------+----------+----------------------------+------------
mt8173-elm-hana | arm64 | lab-collabora | gcc-10 | defconfig+arm64-chromebook | 1
Details: https://kernelci.org/test/plan/id/6376ad385698bae8bb2abd24
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//renesas/master/renesas-devel-2022-11-17-v6.1-rc5/arm64/defconfig+arm64-chromebook/gcc-10/lab-collabora/ltp-ipc-mt8173-elm-hana.txt
HTML log: https://storage.kernelci.org//renesas/master/renesas-devel-2022-11-17-v6.1-rc5/arm64/defconfig+arm64-chromebook/gcc-10/lab-collabora/ltp-ipc-mt8173-elm-hana.html
Rootfs: http://storage.kernelci.org/images/rootfs/debian/bullseye-ltp/20221107.1/arm64/initrd.cpio.gz
* ltp-ipc.login: https://kernelci.org/test/case/id/6376ad385698bae8bb2abd25
new failure (last pass: renesas-devel-2022-11-10-v6.1-rc4)
reply other threads:[~2022-11-17 23:29 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=6376c3ce.630a0220.3237d.2b31@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox