From: "kernelci.org bot" <bot@kernelci.org>
To: linux-renesas-soc@vger.kernel.org, kernelci-results@groups.io
Subject: renesas/master baseline: 61 runs, 1 regressions (renesas-devel-2024-06-28-v6.10-rc5)
Date: Fri, 28 Jun 2024 05:28:20 -0700 (PDT) [thread overview]
Message-ID: <667eac64.050a0220.a85c0.429d@mx.google.com> (raw)
renesas/master baseline: 61 runs, 1 regressions (renesas-devel-2024-06-28-v6.10-rc5)
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-06-28-v6.10-rc5/plan/baseline/
Test: baseline
Tree: renesas
Branch: master
Describe: renesas-devel-2024-06-28-v6.10-rc5
URL: https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git
SHA: b697d5470d57cfd6ff3e1388699cd905334a9220
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/667e7bac7bef8aa4e47e7078
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-06-28-v6.10-rc5/arm/multi_v7_defconfig/gcc-10/lab-cip/baseline-beaglebone-black.txt
HTML log: https://storage.kernelci.org//renesas/master/renesas-devel-2024-06-28-v6.10-rc5/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/667e7bac7bef8aa4e47e707d
failing since 0 day (last pass: renesas-devel-2024-06-25-v6.10-rc5, first fail: renesas-devel-2024-06-27-v6.10-rc5)
1 lines
2024-06-28T09:00:09.333425 / #
2024-06-28T09:00:09.345046
2024-06-28T09:00:09.446926 / # #
2024-06-28T09:00:09.457065 #
2024-06-28T09:00:09.557880 / # export SHELL=/bin/sh
2024-06-28T09:00:09.568910 export SHELL=/bin/sh
2024-06-28T09:00:09.669617 / # . /lava-1158168/environment
2024-06-28T09:00:09.680785 . /lava-1158168/environment
2024-06-28T09:00:09.781522 / # /lava-1158168/bin/lava-test-runner /lava-1158168/0
2024-06-28T09:00:09.792666 /lava-1158168/bin/lava-test-runner /lava-1158168/0
... (9 line(s) more)
reply other threads:[~2024-06-28 12:28 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=667eac64.050a0220.a85c0.429d@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.