✅ PASS: Test report for kernel 4.19.41-rc1-721c545.cki (stable)
Hello,
We ran automated tests on a recent commit from this kernel tree:
Kernel repo: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Commit: f897c76a347c - Linux 4.19.41-rc1
The results of these automated tests are provided below.
Overall result: PASSED
Merge: OK
Compile: OK
Tests: OK
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
`-'______________________________________________________________________________
Compile testing
---------------
We compiled the kernel for 4 architectures:
aarch64:
build options: -j20 INSTALL_MOD_STRIP=1 targz-pkg
configuration: https://artifacts.cki-project.org/builds/aarch64/kernel-stable-aarch64-f897c76a347c330cca7fc03afaa64164eda545f7.config
kernel build: https://artifacts.cki-project.org/builds/aarch64/kernel-stable-aarch64-f897c76a347c330cca7fc03afaa64164eda545f7.tar.gzppc64le:
build options: -j20 INSTALL_MOD_STRIP=1 targz-pkg
configuration: https://artifacts.cki-project.org/builds/ppc64le/kernel-stable-ppc64le-f897c76a347c330cca7fc03afaa64164eda545f7.config
kernel build: https://artifacts.cki-project.org/builds/ppc64le/kernel-stable-ppc64le-f897c76a347c330cca7fc03afaa64164eda545f7.tar.gzs390x:
build options: -j20 INSTALL_MOD_STRIP=1 targz-pkg
configuration: https://artifacts.cki-project.org/builds/s390x/kernel-stable-s390x-f897c76a347c330cca7fc03afaa64164eda545f7.config
kernel build: https://artifacts.cki-project.org/builds/s390x/kernel-stable-s390x-f897c76a347c330cca7fc03afaa64164eda545f7.tar.gz x86_64:
build options: -j20 INSTALL_MOD_STRIP=1 targz-pkg
configuration: https://artifacts.cki-project.org/builds/x86_64/kernel-stable-x86_64-f897c76a347c330cca7fc03afaa64164eda545f7.config
kernel build: https://artifacts.cki-project.org/builds/x86_64/kernel-stable-x86_64-f897c76a347c330cca7fc03afaa64164eda545f7.tar.gzHardware testing
----------------
We booted each kernel and ran the following tests:
aarch64:
✅ Boot test [0]
✅ LTP lite [1]
✅ Loopdev Sanity [2]
✅ Memory function: memfd_create [3]
✅ AMTU (Abstract Machine Test Utility) [4]
✅ Ethernet drivers sanity [5]
✅ httpd: mod_ssl smoke sanity [6]
✅ iotop: sanity [7]
✅ redhat-rpm-config: detect-kabi-provides sanity [8] ✅ redhat-rpm-config: kabi-whitelist-not-found sanity [9] ✅ tuned: tune-processes-through-perf [10]
✅ Usex - version 1.9-29 [11]
✅ lvm thinp sanity [12]
✅ Boot test [0]
✅ xfstests: ext4 [13]
✅ xfstests: xfs [13]
🚧 ✅ Networking route: pmtu [14]
🚧 ✅ audit: audit testsuite test [15]
🚧 ✅ Storage blktests [16]
🚧 ✅ stress: stress-ng [17]
🚧 ✅ selinux-policy: serge-testsuite [18]
ppc64le:
✅ Boot test [0]
✅ LTP lite [1]
✅ Loopdev Sanity [2]
✅ Memory function: memfd_create [3]
✅ AMTU (Abstract Machine Test Utility) [4]
✅ Ethernet drivers sanity [5]
✅ httpd: mod_ssl smoke sanity [6]
✅ iotop: sanity [7]
✅ redhat-rpm-config: detect-kabi-provides sanity [8] ✅ redhat-rpm-config: kabi-whitelist-not-found sanity [9] ✅ tuned: tune-processes-through-perf [10]
✅ Usex - version 1.9-29 [11]
✅ lvm thinp sanity [12]
✅ Boot test [0]
✅ xfstests: ext4 [13]
✅ xfstests: xfs [13]
🚧 ✅ Networking route: pmtu [14]
🚧 ✅ audit: audit testsuite test [15]
🚧 ✅ Storage blktests [16]
🚧 ✅ stress: stress-ng [17]
🚧 ✅ selinux-policy: serge-testsuite [18]
s390x:
✅ Boot test [0]
✅ LTP lite [1]
✅ Loopdev Sanity [2]
✅ Memory function: memfd_create [3]
✅ Ethernet drivers sanity [5]
✅ httpd: mod_ssl smoke sanity [6]
✅ iotop: sanity [7]
✅ redhat-rpm-config: detect-kabi-provides sanity [8] ✅ redhat-rpm-config: kabi-whitelist-not-found sanity [9] ✅ tuned: tune-processes-through-perf [10]
✅ Usex - version 1.9-29 [11]
✅ lvm thinp sanity [12]
✅ Boot test [0]
✅ Boot test [0]
🚧 ✅ Networking route: pmtu [14]
🚧 ✅ audit: audit testsuite test [15]
🚧 ✅ Storage blktests [16]
🚧 ✅ stress: stress-ng [17]
🚧 ✅ kdump: sysrq-c [19]
🚧 ✅ selinux-policy: serge-testsuite [18]
x86_64:
✅ Boot test [0]
✅ Boot test [0]
✅ LTP lite [1]
✅ Loopdev Sanity [2]
✅ Memory function: memfd_create [3]
✅ AMTU (Abstract Machine Test Utility) [4]
✅ Ethernet drivers sanity [5]
✅ httpd: mod_ssl smoke sanity [6]
✅ iotop: sanity [7]
✅ redhat-rpm-config: detect-kabi-provides sanity [8] ✅ redhat-rpm-config: kabi-whitelist-not-found sanity [9] ✅ tuned: tune-processes-through-perf [10]
✅ Usex - version 1.9-29 [11]
✅ lvm thinp sanity [12]
✅ Boot test [0]
✅ Boot test [0]
✅ xfstests: ext4 [13]
✅ xfstests: xfs [13]
🚧 ✅ kdump: sysrq-c [19]
🚧 ✅ Networking route: pmtu [14]
🚧 ✅ audit: audit testsuite test [15]
🚧 ✅ Storage blktests [16]
🚧 ✅ stress: stress-ng [17]
🚧 ✅ kdump: sysrq-c - megaraid_sas [19]
🚧 ✅ selinux-policy: serge-testsuite [18]
Test source:
[0]: https://github.com/CKI-project/tests-beaker/archive/master.zip#distribution/kpkginstall [1]: https://github.com/CKI-project/tests-beaker/archive/master.zip#distribution/ltp/lite [2]: https://github.com/CKI-project/tests-beaker/archive/master.zip#filesystems/loopdev/sanity [3]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/memory/function/memfd_create [4]: https://github.com/CKI-project/tests-beaker/archive/master.zip#misc/amtu [5]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/networking/driver/sanity [6]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/httpd/mod_ssl-smoke [7]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/iotop/sanity [8]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/redhat-rpm-config/detect-kabi-provides [9]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/redhat-rpm-config/kabi-whitelist-not-found [10]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/tuned/tune-processes-through-perf [11]: https://github.com/CKI-project/tests-beaker/archive/master.zip#standards/usex/1.9-29 [12]: https://github.com/CKI-project/tests-beaker/archive/master.zip#storage/lvm/thinp/sanity [13]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/filesystems/xfs/xfstests [14]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/networking/route/pmtu [15]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/audit/audit-testsuite [16]: https://github.com/CKI-project/tests-beaker/archive/master.zip#storage/blk [17]: https://github.com/CKI-project/tests-beaker/archive/master.zip#stress/stress-ng [18]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/packages/selinux-policy/serge-testsuite [19]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/kdump/kdump-sysrq-c
Waived tests (marked with 🚧)
-----------------------------
This test run included waived tests. 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.
Quoted 6 lines · CKI Project
Hello,
We ran automated tests on a recent commit from this kernel tree:
Kernel repo:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Commit:f897c76a347c- Linux 4.19.41-rc1
Here you are testing the linux-stable-rc.git tree, not the linux-stable.git tree, like you do for the 5.0 queue.
Any reason why?
thanks,
greg k-h
Quoted 4 lines · Greg KH
Here you are testing the linux-stable-rc.git tree, not the linux-stable.git tree, like you do for the 5.0 queue.
Any reason why?
We're doing two types of tests right now on stable:
1) Tests against -rc releases that appear in linux-stable-rc
2) Tests against stable-queue patch lists (we apply them to the latest release in linux-stable)
Should we adjust our testing approach?
--
Major Hayden
Quoted 4 lines · Major Hayden
Quoted 3 lines · Greg KH
Here you are testing the linux-stable-rc.git tree, not the linux-stable.git tree, like you do for the 5.0 queue.
Quoted 8 lines
Quoted 1 line
Any reason why?
We're doing two types of tests right now on stable:
1) Tests against -rc releases that appear in linux-stable-rc
2) Tests against stable-queue patch lists (we apply them to the latest release in linux-stable)Should we adjust our testing approach?
Ah, no, I was just confused in that the 5.0 responses seemed to be against the stable queue and the 4.19 only against the -rc tree. Please, testing both would be great!
I'll wait for you all to get the configurations all set up before making any more stupid assumptions :)
thanks,
greg k-h
Quoted 6 lines · Greg KH
Ah, no, I was just confused in that the 5.0 responses seemed to be against the stable queue and the 4.19 only against the -rc tree. Please, testing both would be great!
I'll wait for you all to get the configurations all set up before making any more stupid assumptions :)
Sounds good! :)
--
Major Hayden