From: "kernelci.org bot" <bot@kernelci.org>
To: linux-renesas-soc@vger.kernel.org, kernelci-results@groups.io
Subject: renesas/master baseline: 64 runs, 1 regressions (renesas-devel-2024-04-29-v6.9-rc6)
Date: Mon, 29 Apr 2024 05:31:14 -0700 (PDT) [thread overview]
Message-ID: <662f9312.170a0220.ea70a.809b@mx.google.com> (raw)
renesas/master baseline: 64 runs, 1 regressions (renesas-devel-2024-04-29-v6.9-rc6)
Regressions Summary
-------------------
platform | arch | lab | compiler | defconfig | regressions
-----------------+------+---------+----------+--------------------+------------
beaglebone-black | arm | lab-cip | gcc-10 | multi_v7_defconfig | 1
Details: https://kernelci.org/test/job/renesas/branch/master/kernel/renesas-devel-2024-04-29-v6.9-rc6/plan/baseline/
Test: baseline
Tree: renesas
Branch: master
Describe: renesas-devel-2024-04-29-v6.9-rc6
URL: https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git
SHA: d55c1249af5add856fe96d2f7d3dea96fa61e285
Test Regressions
----------------
platform | arch | lab | compiler | defconfig | regressions
-----------------+------+---------+----------+--------------------+------------
beaglebone-black | arm | lab-cip | gcc-10 | multi_v7_defconfig | 1
Details: https://kernelci.org/test/plan/id/662f64ef03cf90acc74c42e1
Results: 3 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//renesas/master/renesas-devel-2024-04-29-v6.9-rc6/arm/multi_v7_defconfig/gcc-10/lab-cip/baseline-beaglebone-black.txt
HTML log: https://storage.kernelci.org//renesas/master/renesas-devel-2024-04-29-v6.9-rc6/arm/multi_v7_defconfig/gcc-10/lab-cip/baseline-beaglebone-black.html
Rootfs: http://storage.kernelci.org/images/rootfs/buildroot/buildroot-baseline/20230703.0/armel/rootfs.cpio.gz
* baseline.dmesg.crit: https://kernelci.org/test/case/id/662f64ef03cf90acc74c42e6
failing since 6 days (last pass: renesas-devel-2024-04-02-v6.9-rc2, first fail: renesas-devel-2024-04-22-v6.9-rc5)
1 lines
2024-04-29T09:14:09.948533 / #
2024-04-29T09:14:09.956494
2024-04-29T09:14:10.059731 / # #
2024-04-29T09:14:10.068561 #
2024-04-29T09:14:10.170669 / # export SHELL=/bin/sh
2024-04-29T09:14:10.180534 export SHELL=/bin/sh
2024-04-29T09:14:10.282319 / # . /lava-1126181/environment
2024-04-29T09:14:10.292022 . /lava-1126181/environment
2024-04-29T09:14:10.393863 / # /lava-1126181/bin/lava-test-runner /lava-1126181/0
2024-04-29T09:14:10.404384 /lava-1126181/bin/lava-test-runner /lava-1126181/0
... (9 line(s) more)
reply other threads:[~2024-04-29 12:31 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=662f9312.170a0220.ea70a.809b@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 read-only IMAP folder(s) and NNTP newsgroup(s).