* ❌ FAIL (SKIPPED 49 of 328): Test report for master (6.5.0-rc1, mainline.kernel.org-clang, bde7f150)
@ 2023-07-15 15:20 cki-project
0 siblings, 0 replies; 2+ messages in thread
From: cki-project @ 2023-07-15 15:20 UTC (permalink / raw)
To: haliu, bgoncalv, xiawu, xzhou, llvm, yizhan, jiji, yiche, bhe,
zlang, yiyan
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 'pm-6.5-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm
You can find all the details about the test run at
https://datawarehouse.cki-project.org/kcidb/checkouts/96029
One or more kernel tests failed:
Unrecognized or new issues:
aarch64 - Networking cki netfilter test
Logs: https://datawarehouse.cki-project.org/kcidb/tests/8784685
Non-passing subtests:
❌ FAIL iptables-Plain-NAT-test
❌ FAIL ip6tables-Plain-NAT-test
ppc64le - Networking cki netfilter test
Logs: https://datawarehouse.cki-project.org/kcidb/tests/8784942
Non-passing subtests:
❌ FAIL iptables-Plain-NAT-test
❌ FAIL ip6tables-Plain-NAT-test
ppc64le - kdump - sysrq-c
Logs: https://datawarehouse.cki-project.org/kcidb/tests/8784963
Non-passing subtests:
❌ FAIL /kdump/crash-sysrq-c
ppc64le - kdump - file-load
Logs: https://datawarehouse.cki-project.org/kcidb/tests/8784964
Non-passing subtests:
❌ FAIL /kdump/crash-sysrq-c
s390x - Storage - blktests - nvme-tcp
Logs: https://datawarehouse.cki-project.org/kcidb/tests/8784818
Subtests skipped: 7 out of 36
Non-passing subtests:
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/003
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/004
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/005
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/008
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/009
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/010
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/011
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/012
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/013
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/018
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/019
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/020
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/021
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/022
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/023
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/024
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/025
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/026
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/027
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/028
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/029
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/030
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/040
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/047
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/048
s390x - Networking cki netfilter test
Logs: https://datawarehouse.cki-project.org/kcidb/tests/8784840
Non-passing subtests:
❌ FAIL iptables-Plain-NAT-test
❌ FAIL ip6tables-Plain-NAT-test
x86_64 - Storage - blktests - nvme-tcp
Logs: https://datawarehouse.cki-project.org/kcidb/tests/8784725
Subtests skipped: 7 out of 36
Non-passing subtests:
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/003
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/004
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/005
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/008
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/009
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/010
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/011
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/012
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/013
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/018
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/019
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/020
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/021
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/022
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/023
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/024
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/025
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/026
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/027
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/028
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/029
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/030
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/040
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/047
❌ FAIL nvme-tcp: storage/blktests/nvme/nvme-tcp/tests/nvme/048
x86_64 - Networking cki netfilter test
Logs: https://datawarehouse.cki-project.org/kcidb/tests/8784764
x86_64 (debug) - Boot test
Logs: https://datawarehouse.cki-project.org/kcidb/tests/8784874
x86_64 (debug) - POSIX pjd-fstest suites
Logs: https://datawarehouse.cki-project.org/kcidb/tests/8784883
x86_64 (debug) - xfstests - xfs
Logs: https://datawarehouse.cki-project.org/kcidb/tests/8784919
We also see the following known issues which are not related to your changes:
Issue: Storage blktests - blk: /sys/block/n1/uuid: No such file or directory
URL: https://bugzilla.redhat.com/show_bug.cgi?id=2065886
Affected tests:
aarch64 - Storage - blktests - blk
s390x - Storage - blktests - blk
x86_64 - Storage - blktests - blk
Issue: Storage - blktests - nvme-tcp: nvme/013 (run mkfs and data verification fio job on NVMeOF file-backed ns) get stuck
URL: https://gitlab.com/redhat/centos-stream/tests/kernel/kernel-tests/-/issues/1398
Affected tests:
aarch64 - Storage - blktests - nvme-tcp
Issue: Storage - blktests - nvme-tcp: hit test timeout
URL: https://datawarehouse.cki-project.org/kcidb/tests/7523235
Affected tests:
aarch64 - Storage - blktests - nvme-tcp
Issue: kdump - kexec_boot: image_arm64_probe: Bad arm64 image header
URL: https://issues.redhat.com/browse/RHELPLAN-138156
Affected tests:
aarch64 - kdump - kexec_boot
aarch64 - kdump - kexec-file-load
Issue: Firmware test suite: mv: cannot stat 'dtcompilerparser.tab.c': No such file or directory
URL: https://gitlab.com/redhat/centos-stream/tests/kernel/kernel-tests/-/issues/1544
Affected tests:
aarch64 - Firmware test suite
Issue: [upstream] memcpy: detected field-spanning write (size 24) of single field "(char *)name_loc->nameval" at fs/xfs/libxfs/xfs_attr_leaf.c:1559 (size 1)
URL: https://bugzilla.kernel.org/show_bug.cgi?id=217522
Affected tests:
aarch64 - xfstests - xfs
x86_64 - xfstests - xfs
Issue: [upstream] unchecked MSR access error: RDMSR from 0xe2 at rIP: 0xffffffff87090227 (native_read_msr+0x7/0x40) (intel_idle_init_cstates_icpu)
URL: https://lore.kernel.org/all/CA+QYu4qSBdhEgFURu+ouAf2d_JNPbZgCSUaxCLoGzMqDQOLWsQ@mail.gmail.com/
Affected tests:
x86_64 - Boot test
x86_64 - Reboot test
x86_64 (debug) - Boot test
Issue: [upstream] Libkcapi AF_ALG test: Oops in gcm_walk_start/gcm_aes_crypt on s390x
URL: https://linux-regtracking.leemhuis.info/regzbot/regression/lore/CAAUqJDuRkHE8fPgZJGaKjUjd3QfGwzfumuJBmStPqBhubxyk_A@mail.gmail.com/
Affected tests:
s390x - Libkcapi AF_ALG test
Issue: Storage - lvm thinp sanity: FAIL: mkfs.xfs -fd noalign /dev/mapper/myvg-thinvolume1
URL: https://gitlab.com/redhat/centos-stream/tests/kernel/kernel-tests/-/issues/1353
Affected tests:
ppc64le - Storage - lvm thinp sanity
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:
ppc64le - selinux-policy: serge-testsuite
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
`-'
______________________________________________________________________________
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: ❌ FAIL (SKIPPED 49 of 328): Test report for master (6.5.0-rc1, mainline.kernel.org-clang, bde7f150)
[not found] <39782.123071511204000362@us-mta-517.us.mimecast.lan>
@ 2023-07-18 3:01 ` Baoquan He
0 siblings, 0 replies; 2+ messages in thread
From: Baoquan He @ 2023-07-18 3:01 UTC (permalink / raw)
To: cki-project
Cc: haliu, bgoncalv, xiawu, xzhou, llvm, yizhan, jiji, yiche, zlang,
yiyan
On 07/15/23 at 03:20pm, cki-project@redhat.com wrote:
...snip...
> ppc64le - kdump - sysrq-c
> Logs: https://datawarehouse.cki-project.org/kcidb/tests/8784963
> Non-passing subtests:
> ❌ FAIL /kdump/crash-sysrq-c
> ppc64le - kdump - file-load
> Logs: https://datawarehouse.cki-project.org/kcidb/tests/8784964
> Non-passing subtests:
> ❌ FAIL /kdump/crash-sysrq-c
The test_console.log and console.log are all empty. However, I suspect
it's same issue as below bug. And all ppc64le kdump failures should be
the same issue observed on 6.5-rc1+.
Bug 2222526 - kdump failed with the error "Cannot open /proc/vmcore: No such file or directory"
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-07-18 3:01 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <39782.123071511204000362@us-mta-517.us.mimecast.lan>
2023-07-18 3:01 ` ❌ FAIL (SKIPPED 49 of 328): Test report for master (6.5.0-rc1, mainline.kernel.org-clang, bde7f150) Baoquan He
2023-07-15 15:20 cki-project
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 NNTP newsgroup(s).