From: Rachel Sibley <rasibley@redhat.com>
To: CKI Project <cki-project@redhat.com>,
Linux Stable maillist <stable@vger.kernel.org>
Cc: Xiong Zhou <xzhou@redhat.com>
Subject: Re: ❎ FAIL: Test report for kernel 5.1.4-rc1-2683da8.cki (stable)
Date: Mon, 20 May 2019 13:25:25 -0400 [thread overview]
Message-ID: <89b71b36-c9e1-da13-f889-fa38747cdb06@redhat.com> (raw)
In-Reply-To: <cki.30F349B00C.9VYWGI0LHP@redhat.com>
Please disregard, this appears to be an infrastructure failure related
to a timeout when attempting
to curl the rpcgen package, we will look into updating the test to abort
in this case (infra failure), sorry
for the noise !
- Rachel
On 5/20/19 12:59 PM, CKI Project wrote:
> 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: cce3bc9ebd2f - Linux 5.1.4-rc1
>
> 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:
>
> aarch64:
> ❎ xfstests: ext4
>
> 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
> `-'
> ______________________________________________________________________________
>
> 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-aarch64-cce3bc9ebd2fd2d9cfc0bfe53abbf3525a7fab45.config
> kernel build: https://artifacts.cki-project.org/builds/aarch64/kernel-stable-aarch64-cce3bc9ebd2fd2d9cfc0bfe53abbf3525a7fab45.tar.gz
>
> ppc64le:
> build options: -j25 INSTALL_MOD_STRIP=1 targz-pkg
> configuration: https://artifacts.cki-project.org/builds/ppc64le/kernel-stable-ppc64le-cce3bc9ebd2fd2d9cfc0bfe53abbf3525a7fab45.config
> kernel build: https://artifacts.cki-project.org/builds/ppc64le/kernel-stable-ppc64le-cce3bc9ebd2fd2d9cfc0bfe53abbf3525a7fab45.tar.gz
>
> s390x:
> build options: -j25 INSTALL_MOD_STRIP=1 targz-pkg
> configuration: https://artifacts.cki-project.org/builds/s390x/kernel-stable-s390x-cce3bc9ebd2fd2d9cfc0bfe53abbf3525a7fab45.config
> kernel build: https://artifacts.cki-project.org/builds/s390x/kernel-stable-s390x-cce3bc9ebd2fd2d9cfc0bfe53abbf3525a7fab45.tar.gz
>
> x86_64:
> build options: -j25 INSTALL_MOD_STRIP=1 targz-pkg
> configuration: https://artifacts.cki-project.org/builds/x86_64/kernel-stable-x86_64-cce3bc9ebd2fd2d9cfc0bfe53abbf3525a7fab45.config
> kernel build: https://artifacts.cki-project.org/builds/x86_64/kernel-stable-x86_64-cce3bc9ebd2fd2d9cfc0bfe53abbf3525a7fab45.tar.gz
>
>
> Hardware testing
> ----------------
>
> We booted each kernel and ran the following tests:
>
> aarch64:
> ✅ Boot test [0]
> ❎ xfstests: ext4 [1]
> ✅ xfstests: xfs [1]
> ✅ selinux-policy: serge-testsuite [2]
> ✅ Boot test [0]
> ✅ LTP lite [3]
> ✅ Loopdev Sanity [4]
> ✅ Memory function: memfd_create [5]
> ✅ AMTU (Abstract Machine Test Utility) [6]
> ✅ Ethernet drivers sanity [7]
> ✅ audit: audit testsuite test [8]
> ✅ httpd: mod_ssl smoke sanity [9]
> ✅ iotop: sanity [10]
> ✅ redhat-rpm-config: detect-kabi-provides sanity [11]
> ✅ redhat-rpm-config: kabi-whitelist-not-found sanity [12]
> ✅ tuned: tune-processes-through-perf [13]
> ✅ Usex - version 1.9-29 [14]
> ✅ lvm thinp sanity [15]
> ✅ stress: stress-ng [16]
> 🚧 ✅ /kernel/networking/ipv6/Fujitsu-socketapi-test
> 🚧 ✅ Networking sctp-auth: sockopts test [17]
> 🚧 ✅ Networking: igmp conformance test [18]
> 🚧 ✅ Networking route: pmtu [19]
> 🚧 ✅ Networking route_func: local [20]
> 🚧 ✅ Networking route_func: forward [20]
> 🚧 ✅ Networking TCP: keepalive test [21]
> 🚧 ✅ Storage blktests [22]
>
> ppc64le:
> ✅ Boot test [0]
> ✅ LTP lite [3]
> ✅ Loopdev Sanity [4]
> ✅ Memory function: memfd_create [5]
> ✅ AMTU (Abstract Machine Test Utility) [6]
> ✅ Ethernet drivers sanity [7]
> ✅ audit: audit testsuite test [8]
> ✅ httpd: mod_ssl smoke sanity [9]
> ✅ iotop: sanity [10]
> ✅ redhat-rpm-config: detect-kabi-provides sanity [11]
> ✅ redhat-rpm-config: kabi-whitelist-not-found sanity [12]
> ✅ tuned: tune-processes-through-perf [13]
> ✅ Usex - version 1.9-29 [14]
> ✅ lvm thinp sanity [15]
> ✅ stress: stress-ng [16]
> ✅ Boot test [0]
> ✅ xfstests: ext4 [1]
> ✅ xfstests: xfs [1]
> ✅ selinux-policy: serge-testsuite [2]
> 🚧 ✅ /kernel/networking/ipv6/Fujitsu-socketapi-test
> 🚧 ✅ Networking sctp-auth: sockopts test [17]
> 🚧 ✅ Networking route: pmtu [19]
> 🚧 ✅ Networking route_func: local [20]
> 🚧 ✅ Networking route_func: forward [20]
> 🚧 ✅ Networking TCP: keepalive test [21]
> 🚧 ✅ Storage blktests [22]
>
> s390x:
> ✅ Boot test [0]
> ✅ LTP lite [3]
> ✅ Loopdev Sanity [4]
> ✅ Memory function: memfd_create [5]
> ✅ Ethernet drivers sanity [7]
> ✅ audit: audit testsuite test [8]
> ✅ httpd: mod_ssl smoke sanity [9]
> ✅ iotop: sanity [10]
> ✅ redhat-rpm-config: detect-kabi-provides sanity [11]
> ✅ redhat-rpm-config: kabi-whitelist-not-found sanity [12]
> ✅ tuned: tune-processes-through-perf [13]
> ✅ Usex - version 1.9-29 [14]
> ✅ lvm thinp sanity [15]
> ✅ stress: stress-ng [16]
> ✅ Boot test [0]
> ✅ kdump: sysrq-c [23]
> ✅ Boot test [0]
> ✅ selinux-policy: serge-testsuite [2]
> 🚧 ✅ /kernel/networking/ipv6/Fujitsu-socketapi-test
> 🚧 ✅ Networking sctp-auth: sockopts test [17]
> 🚧 ✅ Networking: igmp conformance test [18]
> 🚧 ✅ Networking route: pmtu [19]
> 🚧 ✅ Networking route_func: local [20]
> 🚧 ✅ Networking route_func: forward [20]
> 🚧 ✅ Networking TCP: keepalive test [21]
> 🚧 ✅ Storage blktests [22]
>
> x86_64:
> ✅ Boot test [0]
> ✅ xfstests: ext4 [1]
> ✅ xfstests: xfs [1]
> ✅ selinux-policy: serge-testsuite [2]
> ✅ Boot test [0]
> ✅ LTP lite [3]
> ✅ Loopdev Sanity [4]
> ✅ Memory function: memfd_create [5]
> ✅ AMTU (Abstract Machine Test Utility) [6]
> ✅ Ethernet drivers sanity [7]
> ✅ audit: audit testsuite test [8]
> ✅ httpd: mod_ssl smoke sanity [9]
> ✅ iotop: sanity [10]
> ✅ redhat-rpm-config: detect-kabi-provides sanity [11]
> ✅ redhat-rpm-config: kabi-whitelist-not-found sanity [12]
> ✅ tuned: tune-processes-through-perf [13]
> ✅ Usex - version 1.9-29 [14]
> ✅ lvm thinp sanity [15]
> ✅ stress: stress-ng [16]
> ✅ Boot test [0]
> ✅ kdump: sysrq-c - megaraid_sas [23]
> ✅ Boot test [0]
> ✅ kdump: sysrq-c [23]
> 🚧 ✅ /kernel/networking/ipv6/Fujitsu-socketapi-test
> 🚧 ✅ Networking sctp-auth: sockopts test [17]
> 🚧 ✅ Networking: igmp conformance test [18]
> 🚧 ✅ Networking route: pmtu [19]
> 🚧 ✅ Networking route_func: local [20]
> 🚧 ✅ Networking route_func: forward [20]
> 🚧 ✅ Networking TCP: keepalive test [21]
> 🚧 ✅ Storage blktests [22]
>
> 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#/filesystems/xfs/xfstests
> [2]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/packages/selinux-policy/serge-testsuite
> [3]: https://github.com/CKI-project/tests-beaker/archive/master.zip#distribution/ltp/lite
> [4]: https://github.com/CKI-project/tests-beaker/archive/master.zip#filesystems/loopdev/sanity
> [5]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/memory/function/memfd_create
> [6]: https://github.com/CKI-project/tests-beaker/archive/master.zip#misc/amtu
> [7]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/networking/driver/sanity
> [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/redhat-rpm-config/detect-kabi-provides
> [12]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/redhat-rpm-config/kabi-whitelist-not-found
> [13]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/tuned/tune-processes-through-perf
> [14]: https://github.com/CKI-project/tests-beaker/archive/master.zip#standards/usex/1.9-29
> [15]: https://github.com/CKI-project/tests-beaker/archive/master.zip#storage/lvm/thinp/sanity
> [16]: https://github.com/CKI-project/tests-beaker/archive/master.zip#stress/stress-ng
> [17]: https://github.com/CKI-project/tests-beaker/archive/master.zip#networking/sctp/auth/sockopts
> [18]: https://github.com/CKI-project/tests-beaker/archive/master.zip#networking/igmp/conformance
> [19]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/networking/route/pmtu
> [20]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/networking/route/route_func
> [21]: https://github.com/CKI-project/tests-beaker/archive/master.zip#networking/tcp/tcp_keepalive
> [22]: https://github.com/CKI-project/tests-beaker/archive/master.zip#storage/blk
> [23]: 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.
>
prev parent reply other threads:[~2019-05-20 17:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 16:59 ❎ FAIL: Test report for kernel 5.1.4-rc1-2683da8.cki (stable) CKI Project
2019-05-20 17:25 ` Rachel Sibley [this message]
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=89b71b36-c9e1-da13-f889-fa38747cdb06@redhat.com \
--to=rasibley@redhat.com \
--cc=cki-project@redhat.com \
--cc=stable@vger.kernel.org \
--cc=xzhou@redhat.com \
/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).