From: "kernelci.org bot" <bot@kernelci.org>
To: linux-renesas-soc@vger.kernel.org, kernelci-results@groups.io
Subject: renesas/next baseline: 25 runs, 1 regressions (renesas-next-2024-03-01-v6.8-rc1)
Date: Fri, 01 Mar 2024 16:48:20 -0800 (PST) [thread overview]
Message-ID: <65e27754.170a0220.d2069.18f8@mx.google.com> (raw)
renesas/next baseline: 25 runs, 1 regressions (renesas-next-2024-03-01-v6.8-rc1)
Regressions Summary
-------------------
platform | arch | lab | compiler | defconfig | regressions
-----------------+------+-----------------+----------+--------------------+------------
imx6dl-riotboard | arm | lab-pengutronix | gcc-10 | multi_v7_defconfig | 1
Details: https://kernelci.org/test/job/renesas/branch/next/kernel/renesas-next-2024-03-01-v6.8-rc1/plan/baseline/
Test: baseline
Tree: renesas
Branch: next
Describe: renesas-next-2024-03-01-v6.8-rc1
URL: https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git
SHA: 01fdf7d6f1504ba6a93e7d8eacb27d45dc995325
Test Regressions
----------------
platform | arch | lab | compiler | defconfig | regressions
-----------------+------+-----------------+----------+--------------------+------------
imx6dl-riotboard | arm | lab-pengutronix | gcc-10 | multi_v7_defconfig | 1
Details: https://kernelci.org/test/plan/id/65e24129ae106e8248637012
Results: 5 PASS, 1 FAIL, 1 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//renesas/next/renesas-next-2024-03-01-v6.8-rc1/arm/multi_v7_defconfig/gcc-10/lab-pengutronix/baseline-imx6dl-riotboard.txt
HTML log: https://storage.kernelci.org//renesas/next/renesas-next-2024-03-01-v6.8-rc1/arm/multi_v7_defconfig/gcc-10/lab-pengutronix/baseline-imx6dl-riotboard.html
Rootfs: http://storage.kernelci.org/images/rootfs/buildroot/buildroot-baseline/20230623.0/armel/rootfs.cpio.gz
* baseline.bootrr.deferred-probe-empty: https://kernelci.org/test/case/id/65e24129ae106e8248637017
new failure (last pass: renesas-next-2024-02-23-v6.8-rc1)
2024-03-01T20:57:03.494162 + set[ 15.155052] <LAVA_SIGNAL_ENDRUN 0_dmesg 1031199_1.5.2.3.1>
2024-03-01T20:57:03.494302 +x
2024-03-01T20:57:03.600240 / # #
2024-03-01T20:57:03.701636 export SHELL=/bin/sh
2024-03-01T20:57:03.702151 #
2024-03-01T20:57:03.802960 / # export SHELL=/bin/sh. /lava-1031199/environment
2024-03-01T20:57:03.803403
2024-03-01T20:57:03.904200 / # . /lava-1031199/environment/lava-1031199/bin/lava-test-runner /lava-1031199/1
2024-03-01T20:57:03.904839
2024-03-01T20:57:03.908204 / # /lava-1031199/bin/lava-test-runner /lava-1031199/1
... (12 line(s) more)
reply other threads:[~2024-03-02 0:48 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=65e27754.170a0220.d2069.18f8@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;
as well as URLs for NNTP newsgroup(s).