From: "kernelci.org bot" <bot@kernelci.org>
To: Cipproject+Cip-Dev via Email Integration <cip-dev@lists.cip-project.org>
Subject: cip/linux-4.4.y-cip baseline: 102 runs, 2 regressions (v4.4.294-cip66) #kernelci
Date: Sun, 12 Dec 2021 09:34:43 -0800 (PST) [thread overview]
Message-ID: <61b632b3.1c69fb81.e673b.b195@mx.google.com> (raw)
cip/linux-4.4.y-cip baseline: 102 runs, 2 regressions (v4.4.294-cip66)
Regressions Summary
-------------------
platform | arch | lab | compiler | defconfig | regressions
----------+------+--------------+----------+---------------------+------------
beagle-xm | arm | lab-baylibre | gcc-10 | omap2plus_defconfig | 2
Details: https://kernelci.org/test/job/cip/branch/linux-4.4.y-cip/kernel/v4.4.294-cip66/plan/baseline/
Test: baseline
Tree: cip
Branch: linux-4.4.y-cip
Describe: v4.4.294-cip66
URL: https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git
SHA: f8a9792915e8ad9f417a6431735e953e944713c7
Test Regressions
----------------
platform | arch | lab | compiler | defconfig | regressions
----------+------+--------------+----------+---------------------+------------
beagle-xm | arm | lab-baylibre | gcc-10 | omap2plus_defconfig | 2
Details: https://kernelci.org/test/plan/id/61b624d88cf5d87a1b397160
Results: 3 PASS, 2 FAIL, 1 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.4.y-cip/v4.4.294-cip66/arm/omap2plus_defconfig/gcc-10/lab-baylibre/baseline-beagle-xm.txt
HTML log: https://storage.kernelci.org//cip/linux-4.4.y-cip/v4.4.294-cip66/arm/omap2plus_defconfig/gcc-10/lab-baylibre/baseline-beagle-xm.html
Rootfs: http://storage.kernelci.org/images/rootfs/buildroot/kci-2020.05-6-g8983f3b738df/armel/baseline/rootfs.cpio.gz
* baseline.dmesg.crit: https://kernelci.org/test/case/id/61b624d88cf5d87a1b397163
new failure (last pass: v4.4.291-cip65)
1 lines
2021-12-12T16:35:17.876920 / #
2021-12-12T16:35:17.877955 #
2021-12-12T16:35:17.982598 / # #
2021-12-12T16:35:17.983497
2021-12-12T16:35:18.085106 / # #export SHELL=/bin/sh
2021-12-12T16:35:18.085643
2021-12-12T16:35:18.186941 / # export SHELL=/bin/sh. /lava-1231327/environment
2021-12-12T16:35:18.187444
2021-12-12T16:35:18.288967 / # . /lava-1231327/environment/lava-1231327/bin/lava-test-runner /lava-1231327/0
2021-12-12T16:35:18.290631
... (10 line(s) more)
* baseline.dmesg.emerg: https://kernelci.org/test/case/id/61b624d88cf5d87a1b397165
new failure (last pass: v4.4.291-cip65)
29 lines
2021-12-12T16:35:18.752528 [ 49.458831] <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=alert RESULT=pass UNITS=lines MEASUREMENT=0>
2021-12-12T16:35:18.807403 kern :emerg : Internal error: Oops - BUG: 0 [#1] SMP ARM
2021-12-12T16:35:18.810742 kern :emerg : Process udevd (pid: 110, stack limit = 0xcb942218)
2021-12-12T16:35:18.815236 kern :emerg : Stack: (0xcb943cf8 to 0xcb944000)
2021-12-12T16:35:18.823759 kern :emerg : 3ce0: bf02bdc4 60000013
reply other threads:[~2021-12-12 17:34 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=61b632b3.1c69fb81.e673b.b195@mx.google.com \
--to=bot@kernelci.org \
--cc=cip-dev@lists.cip-project.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