From: "kernelci.org bot" <bot@kernelci.org>
To: cip-dev+int+1680+2922216858170285886@lists.cip-project.org,
kernel-build-reports@lists.linaro.org,
kernelci-results@groups.io
Subject: cip/linux-4.4.y-cip smc: 4 runs, 1 regressions (v4.4.302-cip70-236-g69445bc0d4209)
Date: Tue, 22 Nov 2022 03:56:18 -0800 (PST) [thread overview]
Message-ID: <637cb8e2.a70a0220.705d5.fcc1@mx.google.com> (raw)
cip/linux-4.4.y-cip smc: 4 runs, 1 regressions (v4.4.302-cip70-236-g69445bc0d4209)
Regressions Summary
-------------------
platform | arch | lab | compiler | defconfig | regressions
------------+--------+---------------+----------+------------------+------------
qemu_x86_64 | x86_64 | lab-collabora | gcc-10 | x86_64_defconfig | 1
Details: https://kernelci.org/test/job/cip/branch/linux-4.4.y-cip/kernel/v4.4.302-cip70-236-g69445bc0d4209/plan/smc/
Test: smc
Tree: cip
Branch: linux-4.4.y-cip
Describe: v4.4.302-cip70-236-g69445bc0d4209
URL: https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git
SHA: 69445bc0d4209b0634d1f43657fd58f708cadf81
Test Regressions
----------------
platform | arch | lab | compiler | defconfig | regressions
------------+--------+---------------+----------+------------------+------------
qemu_x86_64 | x86_64 | lab-collabora | gcc-10 | x86_64_defconfig | 1
Details: https://kernelci.org/test/plan/id/637ca8f216bde65afb2abd0f
Results: 14 PASS, 2 FAIL, 0 SKIP
Full config: x86_64_defconfig
Compiler: gcc-10 (gcc (Debian 10.2.1-6) 10.2.1 20210110)
Plain log: https://storage.kernelci.org//cip/linux-4.4.y-cip/v4.4.302-cip70-236-g69445bc0d4209/x86_64/x86_64_defconfig/gcc-10/lab-collabora/smc-qemu_x86_64.txt
HTML log: https://storage.kernelci.org//cip/linux-4.4.y-cip/v4.4.302-cip70-236-g69445bc0d4209/x86_64/x86_64_defconfig/gcc-10/lab-collabora/smc-qemu_x86_64.html
Rootfs: http://storage.kernelci.org/images/rootfs/buildroot/buildroot-baseline/20221107.1/x86/rootfs.cpio.gz
* smc.CVE-2020-0543: https://kernelci.org/test/case/id/637ca8f216bde65afb2abd11
failing since 52 days (last pass: v4.4.302-cip70, first fail: v4.4.302-cip70-98-g7f7838c92740f)
2022-11-22T10:48:07.726743 [ 2.087604] <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=CVE-2018-12207 RESULT=pass>
2022-11-22T10:48:07.726828
2022-11-22T10:48:07.730392 [ 2.091703] <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=CVE-2020-0543 RESULT=fail>
reply other threads:[~2022-11-22 11:56 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=637cb8e2.a70a0220.705d5.fcc1@mx.google.com \
--to=bot@kernelci.org \
--cc=cip-dev+int+1680+2922216858170285886@lists.cip-project.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=kernelci-results@groups.io \
/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.