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-4.19.y-cip ltp-ipc: 10 runs, 2 regressions (v4.19.299-cip105)
Date: Thu, 07 Dec 2023 13:44:18 -0800 (PST) [thread overview]
Message-ID: <65723cb2.170a0220.d923c.1b8a@mx.google.com> (raw)
cip/linux-4.19.y-cip ltp-ipc: 10 runs, 2 regressions (v4.19.299-cip105)
Regressions Summary
-------------------
platform | arch | lab | compiler | defconfig | regressions
-----------------+------+-------------+----------+---------------------+------------
beaglebone-black | arm | lab-broonie | gcc-10 | multi_v7_defconfig | 1
beaglebone-black | arm | lab-broonie | gcc-10 | omap2plus_defconfig | 1
Details: https://kernelci.org/test/job/cip/branch/linux-4.19.y-cip/kernel/v4.19.299-cip105/plan/ltp-ipc/
Test: ltp-ipc
Tree: cip
Branch: linux-4.19.y-cip
Describe: v4.19.299-cip105
URL: https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git
SHA: d152f9dce44a3068c74de8c2046a16b8dd3c1544
Test suite revisions:
ltp-tests
URL: https://github.com/linux-test-project/ltp.git
SHA: 3f0b2176930cf15a26597e28abf4356050136bbe
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/657233ecfa313170e3e1348a
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/linux-4.19.y-cip/v4.19.299-cip105/arm/multi_v7_defconfig/gcc-10/lab-broonie/ltp-ipc-beaglebone-black.txt
HTML log: https://storage.kernelci.org//cip/linux-4.19.y-cip/v4.19.299-cip105/arm/multi_v7_defconfig/gcc-10/lab-broonie/ltp-ipc-beaglebone-black.html
Rootfs: http://storage.kernelci.org/images/rootfs/debian/bullseye-ltp/20230623.0/armhf/initrd.cpio.gz
* ltp-ipc.login: https://kernelci.org/test/case/id/657233ecfa313170e3e1348b
new failure (last pass: v4.19.295-cip103)
platform | arch | lab | compiler | defconfig | regressions
-----------------+------+-------------+----------+---------------------+------------
beaglebone-black | arm | lab-broonie | gcc-10 | omap2plus_defconfig | 1
Details: https://kernelci.org/test/plan/id/6572317acb546c84dae1349c
Results: 0 PASS, 1 FAIL, 0 SKIP
Full config: omap2plus_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-4.19.y-cip/v4.19.299-cip105/arm/omap2plus_defconfig/gcc-10/lab-broonie/ltp-ipc-beaglebone-black.txt
HTML log: https://storage.kernelci.org//cip/linux-4.19.y-cip/v4.19.299-cip105/arm/omap2plus_defconfig/gcc-10/lab-broonie/ltp-ipc-beaglebone-black.html
Rootfs: http://storage.kernelci.org/images/rootfs/debian/bullseye-ltp/20230623.0/armhf/initrd.cpio.gz
* ltp-ipc.login: https://kernelci.org/test/case/id/6572317acb546c84dae1349d
new failure (last pass: v4.19.295-cip103)
reply other threads:[~2023-12-07 21:44 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=65723cb2.170a0220.d923c.1b8a@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.