From: CKI Project <cki-project@redhat.com>
To: Linux Stable maillist <stable@vger.kernel.org>
Cc: Jakub Krysl <jkrysl@redhat.com>
Subject: ❎ FAIL: Stable queue: queue-4.19
Date: Mon, 13 May 2019 09:22:19 -0400 [thread overview]
Message-ID: <cki.02CC569AE1.DRJSZO3WAQ@redhat.com> (raw)
Hello,
We ran automated tests on a patchset that was proposed for merging into this
kernel tree. The patches were applied to:
Kernel repo: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Commit: 9c2556f428cf - Linux 4.19.42
The results of these automated tests are provided below.
Overall result: FAILED (see details below)
Merge: OK
Compile: OK
Tests: FAILED
One or more kernel tests failed:
s390x:
❎ lvm thinp sanity
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: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Commit: 9c2556f428cf - Linux 4.19.42
We then merged the patchset with `git am`:
bfq-update-internal-depth-state-when-queue-depth-cha.patch
platform-x86-sony-laptop-fix-unintentional-fall-through.patch
platform-x86-thinkpad_acpi-disable-bluetooth-for-some-machines.patch
platform-x86-dell-laptop-fix-rfkill-functionality.patch
hwmon-pwm-fan-disable-pwm-if-fetching-cooling-data-fails.patch
kernfs-fix-barrier-usage-in-__kernfs_new_node.patch
virt-vbox-sanity-check-parameter-types-for-hgcm-calls-coming-from-userspace.patch
usb-serial-fix-unthrottle-races.patch
Compile testing
---------------
We compiled the kernel for 4 architectures:
aarch64:
build options: -j25 INSTALL_MOD_STRIP=1 targz-pkg
configuration: https://artifacts.cki-project.org/builds/aarch64/kernel-stable_queue_4.19-aarch64-83cd03102ebf13d864a6d357cc4708ffb12d63d2.config
kernel build: https://artifacts.cki-project.org/builds/aarch64/kernel-stable_queue_4.19-aarch64-83cd03102ebf13d864a6d357cc4708ffb12d63d2.tar.gz
ppc64le:
build options: -j25 INSTALL_MOD_STRIP=1 targz-pkg
configuration: https://artifacts.cki-project.org/builds/ppc64le/kernel-stable_queue_4.19-ppc64le-83cd03102ebf13d864a6d357cc4708ffb12d63d2.config
kernel build: https://artifacts.cki-project.org/builds/ppc64le/kernel-stable_queue_4.19-ppc64le-83cd03102ebf13d864a6d357cc4708ffb12d63d2.tar.gz
s390x:
build options: -j25 INSTALL_MOD_STRIP=1 targz-pkg
configuration: https://artifacts.cki-project.org/builds/s390x/kernel-stable_queue_4.19-s390x-83cd03102ebf13d864a6d357cc4708ffb12d63d2.config
kernel build: https://artifacts.cki-project.org/builds/s390x/kernel-stable_queue_4.19-s390x-83cd03102ebf13d864a6d357cc4708ffb12d63d2.tar.gz
x86_64:
build options: -j25 INSTALL_MOD_STRIP=1 targz-pkg
configuration: https://artifacts.cki-project.org/builds/x86_64/kernel-stable_queue_4.19-x86_64-83cd03102ebf13d864a6d357cc4708ffb12d63d2.config
kernel build: https://artifacts.cki-project.org/builds/x86_64/kernel-stable_queue_4.19-x86_64-83cd03102ebf13d864a6d357cc4708ffb12d63d2.tar.gz
Hardware testing
----------------
We booted each kernel and ran the following tests:
aarch64:
✅ Boot test [0]
✅ Boot test [0]
✅ LTP lite [1]
✅ Loopdev Sanity [2]
✅ AMTU (Abstract Machine Test Utility) [3]
✅ httpd: mod_ssl smoke sanity [4]
✅ iotop: sanity [5]
✅ tuned: tune-processes-through-perf [6]
✅ lvm thinp sanity [7]
🚧 ✅ selinux-policy: serge-testsuite [8]
🚧 ✅ audit: audit testsuite test [9]
🚧 ✅ stress: stress-ng [10]
ppc64le:
✅ Boot test [0]
✅ Boot test [0]
✅ LTP lite [1]
✅ Loopdev Sanity [2]
✅ AMTU (Abstract Machine Test Utility) [3]
✅ httpd: mod_ssl smoke sanity [4]
✅ iotop: sanity [5]
✅ tuned: tune-processes-through-perf [6]
✅ lvm thinp sanity [7]
🚧 ✅ selinux-policy: serge-testsuite [8]
🚧 ✅ audit: audit testsuite test [9]
🚧 ✅ stress: stress-ng [10]
s390x:
✅ Boot test [0]
✅ Boot test [0]
✅ LTP lite [1]
✅ Loopdev Sanity [2]
✅ httpd: mod_ssl smoke sanity [4]
✅ iotop: sanity [5]
✅ tuned: tune-processes-through-perf [6]
❎ lvm thinp sanity [7]
🚧 ✅ selinux-policy: serge-testsuite [8]
🚧 ✅ audit: audit testsuite test [9]
🚧 ✅ stress: stress-ng [10]
x86_64:
✅ Boot test [0]
✅ Boot test [0]
✅ LTP lite [1]
✅ Loopdev Sanity [2]
✅ AMTU (Abstract Machine Test Utility) [3]
✅ httpd: mod_ssl smoke sanity [4]
✅ iotop: sanity [5]
✅ tuned: tune-processes-through-perf [6]
✅ lvm thinp sanity [7]
🚧 ✅ selinux-policy: serge-testsuite [8]
🚧 ✅ audit: audit testsuite test [9]
🚧 ✅ stress: stress-ng [10]
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#misc/amtu
[4]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/httpd/mod_ssl-smoke
[5]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/iotop/sanity
[6]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/tuned/tune-processes-through-perf
[7]: https://github.com/CKI-project/tests-beaker/archive/master.zip#storage/lvm/thinp/sanity
[8]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/packages/selinux-policy/serge-testsuite
[9]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/audit/audit-testsuite
[10]: https://github.com/CKI-project/tests-beaker/archive/master.zip#stress/stress-ng
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.
next reply other threads:[~2019-05-13 13:22 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 13:22 CKI Project [this message]
2019-05-13 14:01 ` ❎ FAIL: Stable queue: queue-4.19 Veronika Kabatova
2019-05-13 15:01 ` Greg KH
2019-05-14 17:41 CKI Project
2019-05-14 17:54 CKI Project
2019-05-17 9:37 CKI Project
2019-05-23 9:33 CKI Project
2019-05-23 9:40 ` Greg KH
2019-05-27 14:59 CKI Project
2019-05-27 15:15 ` Veronika Kabatova
2019-05-31 13:50 CKI Project
2019-05-31 14:17 ` Veronika Kabatova
2019-06-04 9:57 CKI Project
2019-06-04 11:54 ` Greg KH
2019-06-04 13:14 CKI Project
2019-06-04 14:04 CKI Project
2019-06-04 14:34 ` Greg KH
2019-06-15 17:35 CKI Project
2019-06-15 18:51 CKI Project
2019-06-16 3:22 CKI Project
2019-06-16 9:39 CKI Project
2019-06-16 16:01 CKI Project
2019-06-16 16:58 CKI Project
2019-06-17 17:58 CKI Project
2019-06-20 0:12 CKI Project
2019-06-20 5:40 ` Greg KH
2019-06-20 5:37 CKI Project
2019-06-22 9:27 CKI Project
2019-06-24 23:32 CKI Project
2019-06-25 0:47 ` Greg KH
2019-06-25 11:53 ` Major Hayden
2019-06-25 3:41 CKI Project
2019-06-25 3:46 ` Greg KH
2019-07-05 14:12 ❌ " CKI Project
2019-07-08 17:56 CKI Project
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=cki.02CC569AE1.DRJSZO3WAQ@redhat.com \
--to=cki-project@redhat.com \
--cc=jkrysl@redhat.com \
--cc=stable@vger.kernel.org \
/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 NNTP newsgroup(s).