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: e5b9547b1aa3 - Linux 5.0.13
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 `-' ______________________________________________________________________________
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: e5b9547b1aa3 - Linux 5.0.13
We then merged the patchset with `git am`:
selftests-seccomp-prepare-for-exclusive-seccomp-flags.patch seccomp-make-new_listener-and-tsync-flags-exclusive.patch arc-memset-fix-build-with-l1_cache_shift-6.patch iwlwifi-fix-driver-operation-for-5350.patch mwifiex-make-resume-actually-do-something-useful-again-on-sdio-cards.patch mtd-rawnand-marvell-clean-the-controller-state-before-each-operation.patch mac80211-don-t-attempt-to-rename-err_ptr-debugfs-dirs.patch i2c-synquacer-fix-enumeration-of-slave-devices.patch i2c-imx-correct-the-method-of-getting-private-data-in-notifier_call.patch i2c-prevent-runtime-suspend-of-adapter-when-host-notify-is-required.patch alsa-hda-realtek-add-new-dell-platform-for-headset-mode.patch alsa-hda-realtek-fixed-dell-aio-speaker-noise.patch alsa-hda-realtek-apply-the-fixup-for-asus-q325uar.patch usb-yurex-fix-protection-fault-after-device-removal.patch usb-w1-ds2490-fix-bug-caused-by-improper-use-of-altsetting-array.patch usb-dummy-hcd-fix-failure-to-give-back-unlinked-urbs.patch usb-usbip-fix-isoc-packet-num-validation-in-get_pipe.patch usb-core-fix-unterminated-string-returned-by-usb_string.patch usb-core-fix-bug-caused-by-duplicate-interface-pm-usage-counter.patch kvm-lapic-disable-timer-advancement-if-adaptive-tuning-goes-haywire.patch kvm-x86-consider-lapic-tsc-deadline-timer-expired-if-deadline-too-short.patch kvm-lapic-track-lapic-timer-advance-per-vcpu.patch kvm-lapic-allow-user-to-disable-adaptive-tuning-of-timer-advancement.patch kvm-lapic-convert-guest-tsc-to-host-time-domain-if-necessary.patch arm64-dts-rockchip-fix-rk3328-roc-cc-gmac2io-tx-rx_d.patch hid-increase-maximum-report-size-allowed-by-hid_fiel.patch hid-logitech-check-the-return-value-of-create_single.patch hid-debug-fix-race-condition-with-between-rdesc_show.patch rtc-cros-ec-fail-suspend-resume-if-wake-irq-can-t-be.patch rtc-sh-fix-invalid-alarm-warning-for-non-enabled-ala.patch arm-omap2-add-missing-of_node_put-after-of_device_is.patch batman-adv-reduce-claim-hash-refcnt-only-for-removed.patch batman-adv-reduce-tt_local-hash-refcnt-only-for-remo.patch batman-adv-reduce-tt_global-hash-refcnt-only-for-rem.patch batman-adv-fix-warning-in-function-batadv_v_elp_get_.patch arm-dts-rockchip-fix-gpu-opp-node-names-for-rk3288.patch reset-meson-audio-arb-fix-missing-.owner-setting-of-.patch arm-dts-fix-dcan-clkctrl-clock-for-am3.patch i40e-fix-i40e_ptp_adjtime-when-given-a-negative-delt.patch igb-fix-warn_once-on-runtime-suspend.patch ixgbe-fix-mdio-bus-registration.patch i40e-fix-wol-support-check.patch riscv-fix-accessing-8-byte-variable-from-rv32.patch hid-quirks-fix-keyboard-touchpad-on-lenovo-miix-630.patch net-hns3-fix-compile-error.patch xdp-fix-cpumap-redirect-skb-creation-bug.patch net-mlx5-e-switch-protect-from-invalid-memory-access.patch net-mlx5-e-switch-fix-esw-manager-vport-indication-f.patch bonding-show-full-hw-address-in-sysfs-for-slave-entr.patch net-stmmac-use-correct-dma-buffer-size-in-the-rx-des.patch net-stmmac-ratelimit-rx-error-logs.patch net-stmmac-don-t-stop-napi-processing-when-dropping-.patch net-stmmac-don-t-overwrite-discard_frame-status.patch net-stmmac-fix-dropping-of-multi-descriptor-rx-frame.patch net-stmmac-don-t-log-oversized-frames.patch jffs2-fix-use-after-free-on-symlink-traversal.patch debugfs-fix-use-after-free-on-symlink-traversal.patch mfd-twl-core-disable-irq-while-suspended.patch block-use-blk_free_flush_queue-to-free-hctx-fq-in-bl.patch rtc-da9063-set-uie_unsupported-when-relevant.patch hid-input-add-mapping-for-assistant-key.patch vfio-pci-use-correct-format-characters.patch scsi-core-add-new-rdac-lenovo-de_series-device.patch scsi-storvsc-fix-calculation-of-sub-channel-count.patch arm-mach-at91-pm-fix-possible-object-reference-leak.patch blk-mq-do-not-reset-plug-rq_count-before-the-list-is.patch arm64-fix-wrong-check-of-on_sdei_stack-in-nmi-contex.patch net-hns-fix-kasan-use-after-free-in-hns_nic_net_xmit.patch net-hns-use-napi_poll_weight-for-hns-driver.patch net-hns-fix-probabilistic-memory-overwrite-when-hns-.patch net-hns-fix-icmp6-neighbor-solicitation-messages-dis.patch net-hns-fix-warning-when-remove-hns-driver-with-smmu.patch libcxgb-fix-incorrect-ppmax-calculation.patch kvm-svm-prevent-dbg_decrypt-and-dbg_encrypt-overflow.patch kmemleak-powerpc-skip-scanning-holes-in-the-.bss-sec.patch hugetlbfs-fix-memory-leak-for-resv_map.patch sh-fix-multiple-function-definition-build-errors.patch null_blk-prevent-crash-from-bad-home_node-value.patch xsysace-fix-error-handling-in-ace_setup.patch fs-stream_open-opener-for-stream-like-files-so-that-.patch arm-orion-don-t-use-using-64-bit-dma-masks.patch arm-iop-don-t-use-using-64-bit-dma-masks.patch perf-x86-amd-update-generic-hardware-cache-events-for-family-17h.patch bluetooth-btusb-request-wake-pin-with-noautoen.patch bluetooth-mediatek-fix-up-an-error-path-to-restore-bdev-tx_state.patch clk-qcom-add-missing-freq-for-usb30_master_clk-on-8998.patch usb-dwc3-reset-num_trbs-after-skipping.patch staging-iio-adt7316-allow-adt751x-to-use-internal-vref-for-all-dacs.patch staging-iio-adt7316-fix-the-dac-read-calculation.patch staging-iio-adt7316-fix-handling-of-dac-high-resolution-option.patch staging-iio-adt7316-fix-the-dac-write-calculation.patch scsi-hisi_sas-fix-to-only-call-scsi_get_prot_op-for-non-null-scsi_cmnd.patch scsi-rdma-srpt-fix-a-credit-leak-for-aborted-commands.patch asoc-intel-bytcr_rt5651-revert-fix-dmic-map-headsetmic-mapping.patch asoc-rsnd-gen-fix-ssi9-4-5-6-7-busif-related-register-address.patch asoc-sunxi-sun50i-codec-analog-rename-hpvcc-regulator-supply-to-cpvdd.patch asoc-wm_adsp-correct-handling-of-compressed-streams-that-restart.patch asoc-dpcm-skip-missing-substream-while-applying-symmetry.patch asoc-stm32-fix-sai-driver-name-initialisation.patch kvm-vmx-save-rsi-to-an-unused-output-in-the-vcpu-run-asm-blob.patch kvm-nvmx-remove-a-rogue-rax-clobber-from-nested_vmx_check_vmentry_hw.patch kvm-vmx-fix-typos-in-vmentry-vmexit-control-setting.patch kvm-lapic-check-for-in-kernel-lapic-before-deferencing-apic-pointer.patch platform-x86-intel_pmc_core-fix-pch-ip-name.patch platform-x86-intel_pmc_core-handle-cfl-regmap-properly.patch ib-core-unregister-notifier-before-freeing-mad-security.patch ib-core-fix-potential-memory-leak-while-creating-mad-agents.patch ib-core-destroy-qp-if-xrc-qp-fails.patch input-snvs_pwrkey-initialize-necessary-driver-data-before-enabling-irq.patch input-stmfts-acknowledge-that-setting-brightness-is-a-blocking-call.patch gpio-mxc-add-check-to-return-defer-probe-if-clock-tree-not-ready.patch selinux-avoid-silent-denials-in-permissive-mode-under-rcu-walk.patch selinux-never-allow-relabeling-on-context-mounts.patch mac80211-honor-sw_crypto_control-for-unicast-keys-in-ap-vlan-mode.patch powerpc-mm-hash-handle-mmap_min_addr-correctly-in-get_unmapped_area-topdown-search.patch x86-mce-improve-error-message-when-kernel-cannot-recover-p2.patch clk-x86-add-system-specific-quirk-to-mark-clocks-as-critical.patch x86-mm-kaslr-fix-the-size-of-the-direct-mapping-section.patch x86-mm-fix-a-crash-with-kmemleak_scan.patch x86-mm-tlb-revert-x86-mm-align-tlb-invalidation-info.patch i2c-i2c-stm32f7-fix-sdadel-minimum-formula.patch media-v4l2-i2c-ov7670-fix-pll-bypass-register-values.patch asoc-wm_adsp-check-for-buffer-in-trigger-stop.patch mm-kmemleak.c-fix-unused-function-warning.patch
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_queue-aarch64... kernel build: https://artifacts.cki-project.org/builds/aarch64/kernel-stable_queue-aarch64...
ppc64le: build options: -j20 INSTALL_MOD_STRIP=1 targz-pkg configuration: https://artifacts.cki-project.org/builds/ppc64le/kernel-stable_queue-ppc64le... kernel build: https://artifacts.cki-project.org/builds/ppc64le/kernel-stable_queue-ppc64le...
s390x: build options: -j20 INSTALL_MOD_STRIP=1 targz-pkg configuration: https://artifacts.cki-project.org/builds/s390x/kernel-stable_queue-s390x-b25... kernel build: https://artifacts.cki-project.org/builds/s390x/kernel-stable_queue-s390x-b25...
x86_64: build options: -j20 INSTALL_MOD_STRIP=1 targz-pkg configuration: https://artifacts.cki-project.org/builds/x86_64/kernel-stable_queue-x86_64-b... kernel build: https://artifacts.cki-project.org/builds/x86_64/kernel-stable_queue-x86_64-b...
Hardware testing ----------------
We booted each kernel and ran the following tests:
aarch64: ✅ Boot test [0] ✅ xfstests: xfs [1] ✅ Boot test [0] ✅ LTP lite [2] ✅ Loopdev Sanity [3] ✅ AMTU (Abstract Machine Test Utility) [4] ✅ Ethernet drivers sanity [5] ✅ httpd: mod_ssl smoke sanity [6] ✅ iotop: sanity [7] ✅ tuned: tune-processes-through-perf [8] ✅ Usex - version 1.9-29 [9] ✅ lvm thinp sanity [10] 🚧 ✅ selinux-policy: serge-testsuite [11] 🚧 ✅ audit: audit testsuite test [12] 🚧 ✅ stress: stress-ng [13]
ppc64le: ✅ Boot test [0] ✅ LTP lite [2] ✅ Loopdev Sanity [3] ✅ AMTU (Abstract Machine Test Utility) [4] ✅ Ethernet drivers sanity [5] ✅ httpd: mod_ssl smoke sanity [6] ✅ iotop: sanity [7] ✅ tuned: tune-processes-through-perf [8] ✅ Usex - version 1.9-29 [9] ✅ lvm thinp sanity [10] ✅ Boot test [0] ✅ xfstests: xfs [1] 🚧 ✅ audit: audit testsuite test [12] 🚧 ✅ stress: stress-ng [13] 🚧 ✅ selinux-policy: serge-testsuite [11]
s390x: ✅ Boot test [0] ✅ Boot test [0] ✅ LTP lite [2] ✅ Loopdev Sanity [3] ✅ Ethernet drivers sanity [5] ✅ httpd: mod_ssl smoke sanity [6] ✅ iotop: sanity [7] ✅ tuned: tune-processes-through-perf [8] ✅ Usex - version 1.9-29 [9] ✅ lvm thinp sanity [10] 🚧 ✅ selinux-policy: serge-testsuite [11] 🚧 ✅ audit: audit testsuite test [12] 🚧 ✅ stress: stress-ng [13]
x86_64: ✅ Boot test [0] ✅ LTP lite [2] ✅ Loopdev Sanity [3] ✅ AMTU (Abstract Machine Test Utility) [4] ✅ Ethernet drivers sanity [5] ✅ httpd: mod_ssl smoke sanity [6] ✅ iotop: sanity [7] ✅ tuned: tune-processes-through-perf [8] ✅ Usex - version 1.9-29 [9] ✅ lvm thinp sanity [10] ✅ Boot test [0] ✅ xfstests: xfs [1] 🚧 ✅ audit: audit testsuite test [12] 🚧 ✅ stress: stress-ng [13] 🚧 ✅ selinux-policy: serge-testsuite [11]
Test source: [0]: https://github.com/CKI-project/tests-beaker/archive/master.zip#distribution/... [1]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/filesystems/... [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#misc/amtu [5]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/networking/d... [6]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/http... [7]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/ioto... [8]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/tune... [9]: https://github.com/CKI-project/tests-beaker/archive/master.zip#standards/use... [10]: https://github.com/CKI-project/tests-beaker/archive/master.zip#storage/lvm/t... [11]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/packages/sel... [12]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/audi... [13]: https://github.com/CKI-project/tests-beaker/archive/master.zip#stress/stress...
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.
On Tue, May 07, 2019 at 11:21:07AM -0400, CKI Project wrote:
x86_64: ✅ Boot test [0] ✅ LTP lite [2] ✅ Loopdev Sanity [3] ✅ AMTU (Abstract Machine Test Utility) [4] ✅ Ethernet drivers sanity [5] ✅ httpd: mod_ssl smoke sanity [6] ✅ iotop: sanity [7] ✅ tuned: tune-processes-through-perf [8] ✅ Usex - version 1.9-29 [9] ✅ lvm thinp sanity [10] ✅ Boot test [0] ✅ xfstests: xfs [1] 🚧 ✅ audit: audit testsuite test [12] 🚧 ✅ stress: stress-ng [13] 🚧 ✅ selinux-policy: serge-testsuite [11]
Just a question, what is the number in the [] above?
The number of tests run? And if so: ✅ Boot test [0] is listed twice, with no tests run? Doesn't booting count? :)
Also, "LTP lite", isn't that a lot more than just 2 tests that are part of that? Any chance you can add more LTP tests, much like Linaro has? I think their list of LTP tests they are running is somewhere.
Test source: [0]: https://github.com/CKI-project/tests-beaker/archive/master.zip#distribution/... [1]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/filesystems/... [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#misc/amtu [5]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/networking/d... [6]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/http... [7]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/ioto... [8]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/tune... [9]: https://github.com/CKI-project/tests-beaker/archive/master.zip#standards/use... [10]: https://github.com/CKI-project/tests-beaker/archive/master.zip#storage/lvm/t... [11]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/packages/sel... [12]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/audi... [13]: https://github.com/CKI-project/tests-beaker/archive/master.zip#stress/stress...
Ah crap, it's a footnote, nevermind on most of what I wrote above :)
But why is booting happening twice?
And I see you are running xfstests, which is great, but does it really all "pass"? What type of filesystem image are you running it on.
thanks,
greg k-h
----- Original Message -----
From: "Greg KH" gregkh@linuxfoundation.org To: "CKI Project" cki-project@redhat.com Cc: "Linux Stable maillist" stable@vger.kernel.org Sent: Tuesday, May 7, 2019 7:01:50 PM Subject: Re: ✅ PASS: Stable queue: queue-5.0
On Tue, May 07, 2019 at 11:21:07AM -0400, CKI Project wrote:
x86_64: ✅ Boot test [0] ✅ LTP lite [2] ✅ Loopdev Sanity [3] ✅ AMTU (Abstract Machine Test Utility) [4] ✅ Ethernet drivers sanity [5] ✅ httpd: mod_ssl smoke sanity [6] ✅ iotop: sanity [7] ✅ tuned: tune-processes-through-perf [8] ✅ Usex - version 1.9-29 [9] ✅ lvm thinp sanity [10] ✅ Boot test [0] ✅ xfstests: xfs [1] 🚧 ✅ audit: audit testsuite test [12] 🚧 ✅ stress: stress-ng [13] 🚧 ✅ selinux-policy: serge-testsuite [11]
Just a question, what is the number in the [] above?
The number of tests run? And if so: ✅ Boot test [0] is listed twice, with no tests run? Doesn't booting count? :)
Also, "LTP lite", isn't that a lot more than just 2 tests that are part of that? Any chance you can add more LTP tests, much like Linaro has? I think their list of LTP tests they are running is somewhere.
Test source: [0]: https://github.com/CKI-project/tests-beaker/archive/master.zip#distribution/... [1]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/filesystems/... [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#misc/amtu [5]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/networking/d... [6]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/http... [7]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/ioto... [8]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/tune... [9]: https://github.com/CKI-project/tests-beaker/archive/master.zip#standards/use... [10]: https://github.com/CKI-project/tests-beaker/archive/master.zip#storage/lvm/t... [11]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/packages/sel... [12]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/audi... [13]: https://github.com/CKI-project/tests-beaker/archive/master.zip#stress/stress...
Ah crap, it's a footnote, nevermind on most of what I wrote above :)
But why is booting happening twice?
Hi,
in some cases we are running multiple recipes in a single test job, to get out the results faster. Each recipe is started by a "boot test" since that's responsible for installing and booting the kernel being tested. The report joins all recipes for given architecture, hence that one test is shown there multiple times. I agree that we should make this more clear and separate the report parts per recipes but we didn't have time for it yet, sorry. I notified people about the problem and we'll prioritize :)
And I see you are running xfstests, which is great, but does it really all "pass"? What type of filesystem image are you running it on.
Here you can find the list of subtests that's being run [0] and a list of excluded ones from them [1]. This is just a reduced test set as some of the tests were triggering fake failures or taking too long to run as a part of CI. The lists may change in the future of course.
We set up two separate xfs partitions for the testing. The machine should have at least 50G of space available for this.
Hope this explains everything and sorry for the recipe confusion. Let us know if you have anything else!
Veronika CKI Project
[0] https://github.com/CKI-project/tests-beaker/blob/master/filesystems/xfs/xfst... [1] https://github.com/CKI-project/tests-beaker/blob/master/filesystems/xfs/xfst...
thanks,
greg k-h
On Tue, May 07, 2019 at 01:56:34PM -0400, Veronika Kabatova wrote:
----- Original Message -----
From: "Greg KH" gregkh@linuxfoundation.org To: "CKI Project" cki-project@redhat.com Cc: "Linux Stable maillist" stable@vger.kernel.org Sent: Tuesday, May 7, 2019 7:01:50 PM Subject: Re: ✅ PASS: Stable queue: queue-5.0
On Tue, May 07, 2019 at 11:21:07AM -0400, CKI Project wrote:
x86_64: ✅ Boot test [0] ✅ LTP lite [2] ✅ Loopdev Sanity [3] ✅ AMTU (Abstract Machine Test Utility) [4] ✅ Ethernet drivers sanity [5] ✅ httpd: mod_ssl smoke sanity [6] ✅ iotop: sanity [7] ✅ tuned: tune-processes-through-perf [8] ✅ Usex - version 1.9-29 [9] ✅ lvm thinp sanity [10] ✅ Boot test [0] ✅ xfstests: xfs [1] 🚧 ✅ audit: audit testsuite test [12] 🚧 ✅ stress: stress-ng [13] 🚧 ✅ selinux-policy: serge-testsuite [11]
Just a question, what is the number in the [] above?
The number of tests run? And if so: ✅ Boot test [0] is listed twice, with no tests run? Doesn't booting count? :)
Also, "LTP lite", isn't that a lot more than just 2 tests that are part of that? Any chance you can add more LTP tests, much like Linaro has? I think their list of LTP tests they are running is somewhere.
Test source: [0]: https://github.com/CKI-project/tests-beaker/archive/master.zip#distribution/... [1]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/filesystems/... [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#misc/amtu [5]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/networking/d... [6]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/http... [7]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/ioto... [8]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/tune... [9]: https://github.com/CKI-project/tests-beaker/archive/master.zip#standards/use... [10]: https://github.com/CKI-project/tests-beaker/archive/master.zip#storage/lvm/t... [11]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/packages/sel... [12]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/audi... [13]: https://github.com/CKI-project/tests-beaker/archive/master.zip#stress/stress...
Ah crap, it's a footnote, nevermind on most of what I wrote above :)
But why is booting happening twice?
Hi,
in some cases we are running multiple recipes in a single test job, to get out the results faster. Each recipe is started by a "boot test" since that's responsible for installing and booting the kernel being tested. The report joins all recipes for given architecture, hence that one test is shown there multiple times. I agree that we should make this more clear and separate the report parts per recipes but we didn't have time for it yet, sorry. I notified people about the problem and we'll prioritize :)
And I see you are running xfstests, which is great, but does it really all "pass"? What type of filesystem image are you running it on.
Here you can find the list of subtests that's being run [0] and a list of excluded ones from them [1]. This is just a reduced test set as some of the tests were triggering fake failures or taking too long to run as a part of CI. The lists may change in the future of course.
We set up two separate xfs partitions for the testing. The machine should have at least 50G of space available for this.
Hope this explains everything and sorry for the recipe confusion. Let us know if you have anything else!
Thanks a lot for the information. It's good to see that someone is finally running xfstests on the stable trees, that's much appreciated.
greg k-h
On Wed, May 08, 2019 at 11:24:39AM +0200, Greg KH wrote:
Hi,
in some cases we are running multiple recipes in a single test job, to get out the results faster. Each recipe is started by a "boot test" since that's responsible for installing and booting the kernel being tested. The report joins all recipes for given architecture, hence that one test is shown there multiple times. I agree that we should make this more clear and separate the report parts per recipes but we didn't have time for it yet, sorry. I notified people about the problem and we'll prioritize :)
And I see you are running xfstests, which is great, but does it really all "pass"? What type of filesystem image are you running it on.
Here you can find the list of subtests that's being run [0] and a list of excluded ones from them [1]. This is just a reduced test set as some of the tests were triggering fake failures or taking too long to run as a part of CI. The lists may change in the future of course.
We set up two separate xfs partitions for the testing. The machine should have at least 50G of space available for this.
Hope this explains everything and sorry for the recipe confusion. Let us know if you have anything else!
Thanks a lot for the information. It's good to see that someone is finally running xfstests on the stable trees, that's much appreciated.
Hi Greg,
Thanks for the feedback. If you have some other suggested tests, we might be able to add them to our test harness. We do have some bandwidth for extra testing. Thanks!
Cheers, Don
On Wed, May 08, 2019 at 12:22:42PM -0400, Don Zickus wrote:
On Wed, May 08, 2019 at 11:24:39AM +0200, Greg KH wrote:
Hi,
in some cases we are running multiple recipes in a single test job, to get out the results faster. Each recipe is started by a "boot test" since that's responsible for installing and booting the kernel being tested. The report joins all recipes for given architecture, hence that one test is shown there multiple times. I agree that we should make this more clear and separate the report parts per recipes but we didn't have time for it yet, sorry. I notified people about the problem and we'll prioritize :)
And I see you are running xfstests, which is great, but does it really all "pass"? What type of filesystem image are you running it on.
Here you can find the list of subtests that's being run [0] and a list of excluded ones from them [1]. This is just a reduced test set as some of the tests were triggering fake failures or taking too long to run as a part of CI. The lists may change in the future of course.
We set up two separate xfs partitions for the testing. The machine should have at least 50G of space available for this.
Hope this explains everything and sorry for the recipe confusion. Let us know if you have anything else!
Thanks a lot for the information. It's good to see that someone is finally running xfstests on the stable trees, that's much appreciated.
Hi Greg,
Thanks for the feedback. If you have some other suggested tests, we might be able to add them to our test harness. We do have some bandwidth for extra testing. Thanks!
Oh, hey, yes, I do have a list!
It's the list that 0-day does today: https://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git/tree/tests pick some up from there and run with it.
Or look at what Linaro did, they are running a bunch of tests.
Or better yet, work with kernel.ci to integrate runtime tests there so that everyone can benifit!
Having these "closed" testing silos is not good overall. I'm happy to see the kernels get tested, but the duplication of effort is quite sad.
thanks,
greg k-h
linux-stable-mirror@lists.linaro.org