From: CKI Project <cki-project@redhat.com>
To: Linux Stable maillist <stable@vger.kernel.org>
Subject: ✅ PASS: Stable queue: queue-5.2
Date: Wed, 11 Sep 2019 10:08:57 -0400 [thread overview]
Message-ID: <cki.9DF03F9DFA.TADT9Q0WIH@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: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Commit: 997fee5473ce - Linux 5.2.14
The results of these automated tests are provided below.
Overall result: PASSED
Merge: OK
Compile: OK
Tests: OK
All kernel binaries, config files, and logs are available for download here:
https://artifacts.cki-project.org/pipelines/157953
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: 997fee5473ce - Linux 5.2.14
We grabbed the ddfea0b99563 commit of the stable queue repository.
We then merged the patchset with `git am`:
gpio-pca953x-correct-type-of-reg_direction.patch
gpio-pca953x-use-pca953x_read_regs-instead-of-regmap_bulk_read.patch
alsa-hda-fix-potential-endless-loop-at-applying-quirks.patch
alsa-hda-realtek-fix-overridden-device-specific-initialization.patch
alsa-hda-realtek-add-quirk-for-hp-pavilion-15.patch
alsa-hda-realtek-enable-internal-speaker-headset-mic-of-asus-ux431fl.patch
alsa-hda-realtek-fix-the-problem-of-two-front-mics-on-a-thinkcentre.patch
sched-fair-don-t-assign-runtime-for-throttled-cfs_rq.patch
drm-vmwgfx-fix-double-free-in-vmw_recv_msg.patch
drm-nouveau-sec2-gp102-add-missing-module_firmwares.patch
vhost-test-fix-build-for-vhost-test.patch
vhost-test-fix-build-for-vhost-test-again.patch
powerpc-64e-drop-stale-call-to-smp_processor_id-which-hangs-smp-startup.patch
powerpc-tm-fix-fp-vmx-unavailable-exceptions-inside-a-transaction.patch
powerpc-tm-fix-restoring-fp-vmx-facility-incorrectly-on-interrupts.patch
batman-adv-fix-uninit-value-in-batadv_netlink_get_ifindex.patch
batman-adv-only-read-ogm-tvlv_len-after-buffer-len-check.patch
bcache-only-clear-btree_node_dirty-bit-when-it-is-se.patch
bcache-add-comments-for-mutex_lock-b-write_lock.patch
bcache-fix-race-in-btree_flush_write.patch
ib-rdmavt-add-new-completion-inline.patch
ib-rdmavt-qib-hfi1-convert-to-new-completion-api.patch
ib-hfi1-unreserve-a-flushed-opfn-request.patch
drm-i915-disable-sampler_state-prefetching-on-all-ge.patch
drm-i915-userptr-acquire-the-page-lock-around-set_pa.patch
drm-i915-make-sure-cdclk-is-high-enough-for-dp-audio.patch
mmc-sdhci-sprd-fix-the-incorrect-soft-reset-operatio.patch
usb-chipidea-imx-add-imx7ulp-support.patch
usb-chipidea-imx-fix-eprobe_defer-support-during-dri.patch
virtio-s390-fix-race-on-airq_areas.patch
drm-i915-support-flags-in-whitlist-was.patch
drm-i915-support-whitelist-workarounds-on-all-engine.patch
drm-i915-whitelist-ps_-depth-invocation-_count.patch
drm-i915-add-whitelist-workarounds-for-icl.patch
drm-i915-icl-whitelist-ps_-depth-invocation-_count.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]
✅ selinux-policy: serge-testsuite [1]
✅ storage: software RAID testing [2]
Host 2:
✅ Boot test [0]
✅ Podman system integration test (as root) [3]
✅ Podman system integration test (as user) [3]
✅ jvm test suite [4]
✅ AMTU (Abstract Machine Test Utility) [5]
✅ LTP: openposix test suite [6]
✅ Networking socket: fuzz [7]
✅ audit: audit testsuite test [8]
✅ httpd: mod_ssl smoke sanity [9]
✅ iotop: sanity [10]
✅ tuned: tune-processes-through-perf [11]
✅ Usex - version 1.9-29 [12]
✅ stress: stress-ng [13]
🚧 ✅ LTP lite [14]
🚧 ✅ ALSA PCM loopback test [15]
🚧 ✅ ALSA Control (mixer) Userspace Element test [16]
ppc64le:
Host 1:
✅ Boot test [0]
✅ Podman system integration test (as root) [3]
✅ Podman system integration test (as user) [3]
✅ jvm test suite [4]
✅ AMTU (Abstract Machine Test Utility) [5]
✅ LTP: openposix test suite [6]
✅ Networking socket: fuzz [7]
✅ audit: audit testsuite test [8]
✅ httpd: mod_ssl smoke sanity [9]
✅ iotop: sanity [10]
✅ tuned: tune-processes-through-perf [11]
✅ Usex - version 1.9-29 [12]
🚧 ✅ LTP lite [14]
🚧 ✅ ALSA PCM loopback test [15]
🚧 ✅ ALSA Control (mixer) Userspace Element test [16]
Host 2:
✅ Boot test [0]
✅ selinux-policy: serge-testsuite [1]
✅ storage: software RAID testing [2]
x86_64:
Host 1:
✅ Boot test [0]
✅ selinux-policy: serge-testsuite [1]
✅ storage: software RAID testing [2]
Host 2:
⚡ Internal infrastructure issues prevented one or more tests (marked
with ⚡⚡⚡) from running on this architecture.
This is not the fault of the kernel that was tested.
✅ Boot test [0]
✅ Podman system integration test (as root) [3]
✅ Podman system integration test (as user) [3]
✅ jvm test suite [4]
✅ AMTU (Abstract Machine Test Utility) [5]
✅ LTP: openposix test suite [6]
✅ Networking socket: fuzz [7]
✅ audit: audit testsuite test [8]
✅ httpd: mod_ssl smoke sanity [9]
✅ iotop: sanity [10]
✅ tuned: tune-processes-through-perf [11]
✅ pciutils: sanity smoke test [17]
✅ Usex - version 1.9-29 [12]
✅ stress: stress-ng [13]
🚧 ⚡⚡⚡ LTP lite [14]
🚧 ⚡⚡⚡ ALSA PCM loopback test [15]
🚧 ✅ ALSA Control (mixer) Userspace Element test [16]
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/kpkginstall
[1]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/packages/selinux-policy/serge-testsuite
[2]: https://github.com/CKI-project/tests-beaker/archive/master.zip#storage/swraid/trim
[3]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/container/podman
[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/ltp/openposix_testsuite
[7]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/networking/socket/fuzz
[8]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/audit/audit-testsuite
[9]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/httpd/mod_ssl-smoke
[10]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/iotop/sanity
[11]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/tuned/tune-processes-through-perf
[12]: https://github.com/CKI-project/tests-beaker/archive/master.zip#standards/usex/1.9-29
[13]: https://github.com/CKI-project/tests-beaker/archive/master.zip#stress/stress-ng
[14]: https://github.com/CKI-project/tests-beaker/archive/master.zip#distribution/ltp-upstream/lite
[15]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/sound/aloop
[16]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/sound/user-ctl-elem
[17]: https://github.com/CKI-project/tests-beaker/archive/master.zip#pciutils/sanity-smoke
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.
next reply other threads:[~2019-09-11 14:08 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 14:08 CKI Project [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-09-20 7:39 ✅ PASS: Stable queue: queue-5.2 CKI Project
2019-09-20 9:17 ` Veronika Kabatova
2019-09-20 6:17 CKI Project
2019-09-20 0:58 CKI Project
2019-09-19 20:05 CKI Project
2019-09-19 19:56 CKI Project
2019-09-19 18:02 CKI Project
2019-09-19 18:40 ` Major Hayden
2019-09-19 15:36 CKI Project
2019-09-18 4:57 CKI Project
2019-09-18 2:38 CKI Project
2019-09-18 0:29 CKI Project
2019-09-18 0:20 CKI Project
2019-09-17 20:29 CKI Project
2019-09-17 20:23 CKI Project
2019-09-17 12:09 CKI Project
2019-09-17 10:58 CKI Project
2019-09-16 17:53 CKI Project
2019-09-16 4:52 CKI Project
2019-09-13 5:28 CKI Project
2019-09-08 18:46 CKI Project
2019-09-08 14:49 CKI Project
2019-09-08 2:35 CKI Project
2019-09-06 15:20 CKI Project
2019-09-06 0:55 CKI Project
2019-09-05 3:19 CKI Project
2019-09-04 17:20 CKI Project
2019-09-04 9:43 CKI Project
2019-09-04 1:37 CKI Project
2019-09-04 0:50 CKI Project
2019-09-03 13:09 CKI Project
2019-09-03 12:21 CKI Project
2019-09-03 6:23 CKI Project
2019-09-02 23:04 CKI Project
2019-08-30 13:35 CKI Project
2019-08-29 19:35 CKI Project
2019-08-27 9:38 CKI Project
2019-08-27 1:47 CKI Project
2019-08-26 23:55 CKI Project
2019-08-26 23:50 CKI Project
2019-08-26 15:35 CKI Project
2019-08-26 6:14 CKI Project
2019-08-21 5:19 CKI Project
2019-08-21 4:23 CKI Project
2019-08-20 22:57 CKI Project
2019-08-19 7:50 CKI Project
2019-08-18 9:29 CKI Project
2019-08-16 13:31 CKI Project
2019-08-15 6:05 CKI Project
2019-08-15 3:24 CKI Project
2019-08-14 9:17 CKI Project
2019-08-14 2:15 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.9DF03F9DFA.TADT9Q0WIH@redhat.com \
--to=cki-project@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).