Hello,
We ran automated tests on a patchset that was proposed for merging into this kernel tree. The patches were applied to:
Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git Commit: aad39e30fb9e - Linux 5.2.9
The results of these automated tests are provided below.
Overall result: FAILED (see details below) Merge: OK Compile: OK Tests: FAILED
All kernel binaries, config files, and logs are available for download here:
https://artifacts.cki-project.org/pipelines/108109
One or more kernel tests failed:
ppc64le: ❌ selinux-policy: serge-testsuite
We hope that these logs can help you find the problem quickly. For the full detail on our testing procedures, please scroll to the bottom of this message.
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 `-' ______________________________________________________________________________
Merge testing -------------
We cloned this repository and checked out the following commit:
Repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git Commit: aad39e30fb9e - Linux 5.2.9
We grabbed the 6876cde84f1c commit of the stable queue repository.
We then merged the patchset with `git am`:
keys-trusted-allow-module-init-if-tpm-is-inactive-or-deactivated.patch sh-kernel-hw_breakpoint-fix-missing-break-in-switch-statement.patch seq_file-fix-problem-when-seeking-mid-record.patch mm-hmm-fix-bad-subpage-pointer-in-try_to_unmap_one.patch mm-mempolicy-make-the-behavior-consistent-when-mpol_mf_move-and-mpol_mf_strict-were-specified.patch mm-mempolicy-handle-vma-with-unmovable-pages-mapped-correctly-in-mbind.patch mm-z3fold.c-fix-z3fold_destroy_pool-ordering.patch mm-z3fold.c-fix-z3fold_destroy_pool-race-condition.patch mm-memcontrol.c-fix-use-after-free-in-mem_cgroup_iter.patch mm-usercopy-use-memory-range-to-be-accessed-for-wraparound-check.patch mm-vmscan-do-not-special-case-slab-reclaim-when-watermarks-are-boosted.patch cpufreq-schedutil-don-t-skip-freq-update-when-limits-change.patch drm-amdgpu-fix-gfx9-soft-recovery.patch drm-nouveau-only-recalculate-pbn-vcpi-on-mode-connector-changes.patch xtensa-add-missing-isync-to-the-cpu_reset-tlb-code.patch arm64-ftrace-ensure-module-ftrace-trampoline-is-coherent-with-i-side.patch alsa-hda-realtek-add-quirk-for-hp-envy-x360.patch alsa-usb-audio-fix-a-stack-buffer-overflow-bug-in-check_input_term.patch alsa-usb-audio-fix-an-oob-bug-in-parse_audio_mixer_unit.patch alsa-hda-apply-workaround-for-another-amd-chip-1022-1487.patch alsa-hda-fix-a-memory-leak-bug.patch alsa-hda-add-a-generic-reboot_notify.patch alsa-hda-let-all-conexant-codec-enter-d3-when-rebooting.patch
Compile testing ---------------
We compiled the kernel for 3 architectures:
aarch64: make options: -j30 INSTALL_MOD_STRIP=1 targz-pkg
ppc64le: make options: -j30 INSTALL_MOD_STRIP=1 targz-pkg
x86_64: make options: -j30 INSTALL_MOD_STRIP=1 targz-pkg
Hardware testing ---------------- We booted each kernel and ran the following tests:
aarch64: Host 1: ✅ Boot test [0] ✅ Podman system integration test (as root) [1] ✅ Podman system integration test (as user) [1] ✅ LTP lite [2] ✅ Loopdev Sanity [3] ✅ jvm test suite [4] ✅ AMTU (Abstract Machine Test Utility) [5] ✅ LTP: openposix test suite [6] ✅ audit: audit testsuite test [7] ✅ httpd: mod_ssl smoke sanity [8] ✅ iotop: sanity [9] ✅ tuned: tune-processes-through-perf [10] ✅ Usex - version 1.9-29 [11]
Host 2: ✅ Boot test [0] ✅ xfstests: xfs [12] ✅ selinux-policy: serge-testsuite [13]
ppc64le: Host 1: ✅ Boot test [0] ✅ xfstests: xfs [12] ❌ selinux-policy: serge-testsuite [13]
Host 2: ✅ Boot test [0] ✅ Podman system integration test (as root) [1] ✅ Podman system integration test (as user) [1] ✅ LTP lite [2] ✅ Loopdev Sanity [3] ✅ jvm test suite [4] ✅ AMTU (Abstract Machine Test Utility) [5] ✅ LTP: openposix test suite [6] ✅ audit: audit testsuite test [7] ✅ httpd: mod_ssl smoke sanity [8] ✅ iotop: sanity [9] ✅ tuned: tune-processes-through-perf [10] ✅ Usex - version 1.9-29 [11]
x86_64: Host 1: ✅ Boot test [0] ✅ Podman system integration test (as root) [1] ✅ Podman system integration test (as user) [1] ✅ LTP lite [2] ✅ Loopdev Sanity [3] ✅ jvm test suite [4] ✅ AMTU (Abstract Machine Test Utility) [5] ✅ LTP: openposix test suite [6] ✅ audit: audit testsuite test [7] ✅ httpd: mod_ssl smoke sanity [8] ✅ iotop: sanity [9] ✅ tuned: tune-processes-through-perf [10] ✅ pciutils: sanity smoke test [14] ✅ Usex - version 1.9-29 [11] ✅ stress: stress-ng [15]
Host 2: ✅ Boot test [0] ✅ xfstests: xfs [12] ✅ selinux-policy: serge-testsuite [13]
Test source: 💚 Pull requests are welcome for new tests or improvements to existing tests! [0]: https://github.com/CKI-project/tests-beaker/archive/master.zip#distribution/... [1]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/container/po... [2]: https://github.com/CKI-project/tests-beaker/archive/master.zip#distribution/... [3]: https://github.com/CKI-project/tests-beaker/archive/master.zip#filesystems/l... [4]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/jvm [5]: https://github.com/CKI-project/tests-beaker/archive/master.zip#misc/amtu [6]: https://github.com/CKI-project/tests-beaker/archive/master.zip#distribution/... [7]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/audi... [8]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/http... [9]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/ioto... [10]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/tune... [11]: https://github.com/CKI-project/tests-beaker/archive/master.zip#standards/use... [12]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/filesystems/... [13]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/packages/sel... [14]: https://github.com/CKI-project/tests-beaker/archive/master.zip#pciutils/sani... [15]: https://github.com/CKI-project/tests-beaker/archive/master.zip#stress/stress...
Waived tests ------------ If the test run included waived tests, they are marked with 🚧. Such tests are executed but their results are not taken into account. Tests are waived when their results are not reliable enough, e.g. when they're just introduced or are being fixed.