From: cki-project@redhat.com
To: jishi@redhat.com, zlang@redhat.com, haliu@redhat.com,
yiche@redhat.com, jiji@redhat.com, bgoncalv@redhat.com,
llvm@lists.linux.dev, xzhou@redhat.com
Subject: ❌ FAIL (MISSED 10 of 204): Test report for master (6.9.0, mainline.kernel.org-clang, b9dd56e8)
Date: Wed, 22 May 2024 10:51:51 -0000 [thread overview]
Message-ID: <19398.124052206515200318@us-mta-586.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 'soundwire-6.10-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/soundwire
You can find all the details about the test run at
https://datawarehouse.cki-project.org/kcidb/checkouts/redhat:1299678693
One or more kernel tests failed:
Unrecognized or new issues:
Boot test
x86_64 (debug)
Logs: https://datawarehouse.cki-project.org/kcidb/tests/redhat:1299678693-x86_64-kernel-debug_upt_4
Non-passing ran subtests:
❌ FAIL distribution/kpkginstall/journalctl-check
Networking cki netfilter test
ppc64le
Logs: https://datawarehouse.cki-project.org/kcidb/tests/redhat:1299678693-ppc64le-kernel_upt_10
Non-passing ran subtests:
❌ FAIL /10_avc_check
Networking vnic: ipvlan/basic
ppc64le
Logs: https://datawarehouse.cki-project.org/kcidb/tests/redhat:1299678693-ppc64le-kernel_upt_11
Non-passing ran subtests:
❌ FAIL /10_avc_check
POSIX pjd-fstest suites
ppc64le
Logs: https://datawarehouse.cki-project.org/kcidb/tests/redhat:1299678693-ppc64le-kernel_upt_5
Non-passing ran subtests:
❌ FAIL /10_avc_check
Reboot test
x86_64 (debug)
Logs: https://datawarehouse.cki-project.org/kcidb/tests/redhat:1299678693-x86_64-kernel-debug_upt_6
Non-passing ran subtests:
❌ FAIL misc/reboot-test/journalctl-check
xfstests - cifsv3.11
x86_64
Logs: https://datawarehouse.cki-project.org/kcidb/tests/redhat:1299678693-x86_64-kernel_upt_52
Non-passing ran subtests:
❌ FAIL generic/590
x86_64 (debug)
Logs: https://datawarehouse.cki-project.org/kcidb/tests/redhat:1299678693-x86_64-kernel-debug_upt_32
Non-passing ran subtests:
❌ FAIL generic/590
We also see the following known issues which are not related to your changes:
Issue: [rawhide] SELinux is preventing systemd-userdbd from map_read, map_write access on the bpf labeled init_t.
URL: https://bugzilla.redhat.com/show_bug.cgi?id=2250930
Affected tests:
Hardware - Firmware test suite [aarch64]
Networking cki netfilter test [aarch64, s390x, x86_64]
Networking vnic: ipvlan/basic [aarch64, s390x, x86_64]
POSIX pjd-fstest suites [aarch64, s390x, x86_64]
Storage - blktests - blk - upstream [aarch64, x86_64]
stress: stress-ng - cpu-cache [aarch64, x86_64]
stress: stress-ng - memory [aarch64, x86_64]
xfstests - btrfs [aarch64, x86_64]
xfstests - ext4 [aarch64, x86_64]
xfstests - xfs [aarch64, x86_64]
Issue: [eln] avc: denied { create } for pid=1 comm="systemd" scontext=system_u:system_r:init_t:s0 tcontext=system_u:system_r:sshd_t:s0-s0:c0.c1023 tclass=vsock_socket permissive=1
URL: https://bugzilla.redhat.com/show_bug.cgi?id=2280320
Affected tests:
Boot test [aarch64, ppc64le, s390x, x86_64]
Reboot test [aarch64, ppc64le, s390x, x86_64]
Issue: avc: denied { name_bind } for pid=897864 comm="rpcbind" src=63924 scontext=system_u:system_r:rpcbind_t:s0 tcontext=system_u:object_r:unreserved_port_t:s0 tclass=udp_socket permissive=1
URL: https://bugzilla.redhat.com/show_bug.cgi?id=1758147
Affected tests:
xfstests - nfsv4.2 [x86_64]
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: [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]
Networking cki netfilter test [s390x]
Networking vnic: ipvlan/basic [s390x]
POSIX pjd-fstest suites [s390x]
Tests that were not ran because of internal issues:
Boot test [s390x]
CKI/restraint [s390x]
machineinfo [s390x]
Reboot test [s390x]
SELinux Custom Module Setup [s390x]
Storage - blktests - blk - upstream [s390x]
Storage - blktests - nvme-tcp - upstream [s390x]
Storage - swraid scsi_raid [s390x]
stress: stress-ng - cpu-cache [s390x]
stress: stress-ng - memory [s390x]
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-22 10:51 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=19398.124052206515200318@us-mta-586.us.mimecast.lan \
--to=cki-project@redhat.com \
--cc=bgoncalv@redhat.com \
--cc=haliu@redhat.com \
--cc=jiji@redhat.com \
--cc=jishi@redhat.com \
--cc=llvm@lists.linux.dev \
--cc=xzhou@redhat.com \
--cc=yiche@redhat.com \
--cc=zlang@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).