From: "kernelci.org bot" <bot@kernelci.org>
To: linux-next@vger.kernel.org,
kernel-build-reports@lists.linaro.org,
kernelci-results@groups.io
Subject: next/pending-fixes baseline: 70 runs, 1 regressions (v6.9-rc6-205-g3e8ecb3dccc6c)
Date: Tue, 30 Apr 2024 04:32:34 -0700 (PDT) [thread overview]
Message-ID: <6630d6d2.170a0220.7ab95.903d@mx.google.com> (raw)
next/pending-fixes baseline: 70 runs, 1 regressions (v6.9-rc6-205-g3e8ecb3dccc6c)
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/next/branch/pending-fixes/kernel/v6.9-rc6-205-g3e8ecb3dccc6c/plan/baseline/
Test: baseline
Tree: next
Branch: pending-fixes
Describe: v6.9-rc6-205-g3e8ecb3dccc6c
URL: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
SHA: 3e8ecb3dccc6c5d4be4ec8b03bfe74f76e57697d
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/6630a940d7cc48b8184c42ea
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//next/pending-fixes/v6.9-rc6-205-g3e8ecb3dccc6c/arm/multi_v7_defconfig/gcc-10/lab-cip/baseline-beaglebone-black.txt
HTML log: https://storage.kernelci.org//next/pending-fixes/v6.9-rc6-205-g3e8ecb3dccc6c/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/6630a941d7cc48b8184c42ef
new failure (last pass: v6.9-rc5-365-g68d7c66c8435)
1 lines
2024-04-30T08:17:50.611406 / #
2024-04-30T08:17:50.620230
2024-04-30T08:17:50.726249 / # #
2024-04-30T08:17:50.731975 #
2024-04-30T08:17:50.850002 / # export SHELL=/bin/sh
2024-04-30T08:17:50.860074 export SHELL=/bin/sh
2024-04-30T08:17:50.961955 / # . /lava-1126418/environment
2024-04-30T08:17:50.971867 . /lava-1126418/environment
2024-04-30T08:17:51.073791 / # /lava-1126418/bin/lava-test-runner /lava-1126418/0
2024-04-30T08:17:51.083808 /lava-1126418/bin/lava-test-runner /lava-1126418/0
... (9 line(s) more)
reply other threads:[~2024-04-30 11:32 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=6630d6d2.170a0220.7ab95.903d@mx.google.com \
--to=bot@kernelci.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=kernelci-results@groups.io \
--cc=linux-next@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).