From: cki-project@redhat.com
To: xiawu@redhat.com, bgoncalv@redhat.com, xzhou@redhat.com,
yiyan@redhat.com, bhe@redhat.com, llvm@lists.linux.dev
Subject: ❌ FAIL (MISSED 6 of 204): Test report for master (6.9.0, mainline.kernel.org-clang, a7c840ba)
Date: Tue, 14 May 2024 09:30:40 -0000 [thread overview]
Message-ID: <01543.124051405304100170@us-mta-509.us.mimecast.lan> (raw)
Hi, we tested your kernel and here are the results:
Overall result: FAILED
Merge: OK
Compile: OK
Test: FAILED
Kernel information:
Commit message: Merge tag 'tag-chrome-platform-firmware-for-v6.10' of git://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux
You can find all the details about the test run at
https://datawarehouse.cki-project.org/kcidb/checkouts/redhat:1289358699
One or more kernel tests failed:
Unrecognized or new issues:
kdump - kexec-file-load
x86_64
Logs: https://datawarehouse.cki-project.org/kcidb/tests/redhat:1289358699-x86_64-kernel_upt_26
Non-passing ran subtests:
❌ FAIL /kdump/kexec-file-load
Reboot test
x86_64
Logs: https://datawarehouse.cki-project.org/kcidb/tests/redhat:1289358699-x86_64-kernel_upt_37
Non-passing ran subtests:
❌ FAIL misc/reboot-test/journalctl-check
xfstests - cifsv3.11
x86_64
Logs: https://datawarehouse.cki-project.org/kcidb/tests/redhat:1289358699-x86_64-kernel_upt_52
Non-passing ran subtests:
❌ FAIL generic/001
⚡ ERROR /10_localwatchdog
x86_64 (debug)
Logs: https://datawarehouse.cki-project.org/kcidb/tests/redhat:1289358699-x86_64-kernel-debug_upt_32
Non-passing ran subtests:
❌ FAIL Panic
We also see the following known issues which are not related to your changes:
Issue: (ppc64le) selinux-policy: serge-testsuite: ld: cannot find arch/powerpc/lib/crtsavres.o: No such file or directory
URL: https://gitlab.com/redhat/centos-stream/tests/kernel/kernel-tests/-/issues/1267
Affected tests:
selinux-policy: serge-testsuite [ppc64le]
Issue: [upstream] blktests tests/zbd/010 failed (WARNING: CPU: 22 PID: 44011 at fs/iomap/iter.c:51)
URL: https://lore.kernel.org/linux-block/CAHj4cs-kfojYC9i0G73PRkYzcxCTex=-vugRFeP40g_URGvnfQ@mail.gmail.com/T/#u
Affected tests:
Storage - blktests - blk - upstream [aarch64, s390x, x86_64]
Issue: [upstream] stress-ng: avc denial on secretmemory
URL: https://gitlab.com/redhat/centos-stream/tests/kernel/kernel-tests/-/issues/1752
Affected tests:
stress: stress-ng - memory [aarch64, s390x, x86_64]
Issue: [rawhide] [s390x] avc: denied { read write } for pid=12701 comm="systemd-user-ru" name="z90crypt" dev="devtmpfs" ino=103 scontext=system_u:system_r:systemd_logind_t:s0 tcontext=system_u:object_r:crypt_device_t:s0 tclass=chr_file permissive=1
URL: https://bugzilla.redhat.com/show_bug.cgi?id=2263825
Affected tests:
Boot test [s390x]
Filesystem - Loopdev Sanity [s390x]
Libkcapi AF_ALG test [s390x]
machineinfo [s390x]
Networking cki netfilter test [s390x]
Networking vnic: ipvlan/basic [s390x]
POSIX pjd-fstest suites [s390x]
Reboot test [s390x]
Storage - blktests - blk - upstream [s390x]
Storage - blktests - nvme-tcp - upstream [s390x]
stress: stress-ng - cpu-cache [s390x]
stress: stress-ng - memory [s390x]
Tests that were not ran because of internal issues:
Memory function: memfd_create [aarch64, ppc64le, s390x, x86_64, x86_64 (debug)]
Reboot test [x86_64 (debug)]
If you find a failure unrelated to your changes, please ask the test maintainer to review it.
This will prevent the failures from being incorrectly reported in the future.
Please reply to this email if you have any questions about the tests that we
ran or if you have any suggestions on how to make future tests more effective.
,-. ,-.
( C ) ( K ) Continuous
`-',-.`-' Kernel
( I ) Integration
`-'
______________________________________________________________________________
reply other threads:[~2024-05-14 9: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=01543.124051405304100170@us-mta-509.us.mimecast.lan \
--to=cki-project@redhat.com \
--cc=bgoncalv@redhat.com \
--cc=bhe@redhat.com \
--cc=llvm@lists.linux.dev \
--cc=xiawu@redhat.com \
--cc=xzhou@redhat.com \
--cc=yiyan@redhat.com \
/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).