stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Veronika Kabatova <vkabatov@redhat.com>
To: CKI Project <cki-project@redhat.com>, Jeff Bastian <jbastian@redhat.com>
Cc: Linux Stable maillist <stable@vger.kernel.org>
Subject: Re: ❎ FAIL: Stable queue: queue-4.19
Date: Mon, 27 May 2019 11:15:15 -0400 (EDT)	[thread overview]
Message-ID: <2121614321.22097475.1558970115077.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <cki.B161FA3ED6.QK4BD0NMSJ@redhat.com>



----- Original Message -----
> From: "CKI Project" <cki-project@redhat.com>
> To: "Linux Stable maillist" <stable@vger.kernel.org>
> Sent: Monday, May 27, 2019 4:59:46 PM
> Subject: ❎ FAIL: Stable queue: queue-4.19
> 
> 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: 8b2fc0058255 - Linux 4.19.46
> 
> 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:
> 

It didn't fail. stress-ng got into oom situation on aarch64 and we don't seem
to be reporting this kind of warning properly, since the summary says fail but
the actual test list reports everything passed. Sorry.

Jeff, can you take a look whether this is a test issue that needs to be worked
around or if the test caught something? The machine has 16G RAM and 224 cores
so maybe something doesn't scale properly?


Thanks,
Veronika

> 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: 8b2fc0058255 - Linux 4.19.46
> 
> 
> We then merged the patchset with `git am`:
> 
>   x86-hide-the-int3_emulate_call-jmp-functions-from-uml.patch
>   ext4-do-not-delete-unlinked-inode-from-orphan-list-on-failed-truncate.patch
>   ext4-wait-for-outstanding-dio-during-truncate-in-nojournal-mode.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-d33319c71d2e4a6c16e392a4301d425521d7b9cd.config
>     kernel build:
>     https://artifacts.cki-project.org/builds/aarch64/kernel-stable_queue_4.19-aarch64-d33319c71d2e4a6c16e392a4301d425521d7b9cd.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-d33319c71d2e4a6c16e392a4301d425521d7b9cd.config
>     kernel build:
>     https://artifacts.cki-project.org/builds/ppc64le/kernel-stable_queue_4.19-ppc64le-d33319c71d2e4a6c16e392a4301d425521d7b9cd.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-d33319c71d2e4a6c16e392a4301d425521d7b9cd.config
>     kernel build:
>     https://artifacts.cki-project.org/builds/s390x/kernel-stable_queue_4.19-s390x-d33319c71d2e4a6c16e392a4301d425521d7b9cd.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-d33319c71d2e4a6c16e392a4301d425521d7b9cd.config
>     kernel build:
>     https://artifacts.cki-project.org/builds/x86_64/kernel-stable_queue_4.19-x86_64-d33319c71d2e4a6c16e392a4301d425521d7b9cd.tar.gz
> 
> 
> Hardware testing
> ----------------
> 
> We booted each kernel and ran the following tests:
> 
>   aarch64:
>      ✅ Boot test [0]
>      ✅ LTP lite [1]
>      ✅ Loopdev Sanity [2]
>      ✅ AMTU (Abstract Machine Test Utility) [3]
>      ✅ audit: audit testsuite test [4]
>      ✅ httpd: mod_ssl smoke sanity [5]
>      ✅ iotop: sanity [6]
>      ✅ tuned: tune-processes-through-perf [7]
>      ✅ stress: stress-ng [8]
>      ✅ Boot test [0]
>      ✅ xfstests: ext4 [9]
>      ✅ selinux-policy: serge-testsuite [10]
> 
>   ppc64le:
>      ✅ Boot test [0]
>      ✅ xfstests: ext4 [9]
>      ✅ selinux-policy: serge-testsuite [10]
>      ✅ Boot test [0]
>      ✅ LTP lite [1]
>      ✅ Loopdev Sanity [2]
>      ✅ AMTU (Abstract Machine Test Utility) [3]
>      ✅ audit: audit testsuite test [4]
>      ✅ httpd: mod_ssl smoke sanity [5]
>      ✅ iotop: sanity [6]
>      ✅ tuned: tune-processes-through-perf [7]
>      ✅ stress: stress-ng [8]
> 
>   s390x:
>      ✅ Boot test [0]
>      ✅ LTP lite [1]
>      ✅ Loopdev Sanity [2]
>      ✅ audit: audit testsuite test [4]
>      ✅ httpd: mod_ssl smoke sanity [5]
>      ✅ iotop: sanity [6]
>      ✅ tuned: tune-processes-through-perf [7]
>      ✅ stress: stress-ng [8]
>      ✅ Boot test [0]
>      ✅ selinux-policy: serge-testsuite [10]
> 
>   x86_64:
>      ✅ Boot test [0]
>      ✅ xfstests: ext4 [9]
>      ✅ selinux-policy: serge-testsuite [10]
>      ✅ Boot test [0]
>      ✅ LTP lite [1]
>      ✅ Loopdev Sanity [2]
>      ✅ AMTU (Abstract Machine Test Utility) [3]
>      ✅ audit: audit testsuite test [4]
>      ✅ httpd: mod_ssl smoke sanity [5]
>      ✅ iotop: sanity [6]
>      ✅ tuned: tune-processes-through-perf [7]
>      ✅ stress: stress-ng [8]
> 
>   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#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/audit/audit-testsuite
>     [5]:
>     https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/httpd/mod_ssl-smoke
>     [6]:
>     https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/iotop/sanity
>     [7]:
>     https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/tuned/tune-processes-through-perf
>     [8]:
>     https://github.com/CKI-project/tests-beaker/archive/master.zip#stress/stress-ng
>     [9]:
>     https://github.com/CKI-project/tests-beaker/archive/master.zip#/filesystems/xfs/xfstests
>     [10]:
>     https://github.com/CKI-project/tests-beaker/archive/master.zip#/packages/selinux-policy/serge-testsuite
> 
> 
> 

  reply	other threads:[~2019-05-27 15:15 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-27 14:59 ❎ FAIL: Stable queue: queue-4.19 CKI Project
2019-05-27 15:15 ` Veronika Kabatova [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-07-08 17:56  " CKI Project
2019-07-05 14:12 CKI Project
2019-06-25  3:41  " CKI Project
2019-06-25  3:46 ` Greg KH
2019-06-24 23:32 CKI Project
2019-06-25  0:47 ` Greg KH
2019-06-25 11:53   ` Major Hayden
2019-06-22  9:27 CKI Project
2019-06-20  5:37 CKI Project
2019-06-20  0:12 CKI Project
2019-06-20  5:40 ` Greg KH
2019-06-17 17:58 CKI Project
2019-06-16 16:58 CKI Project
2019-06-16 16:01 CKI Project
2019-06-16  9:39 CKI Project
2019-06-16  3:22 CKI Project
2019-06-15 18:51 CKI Project
2019-06-15 17:35 CKI Project
2019-06-04 14:04 CKI Project
2019-06-04 14:34 ` Greg KH
2019-06-04 13:14 CKI Project
2019-06-04  9:57 CKI Project
2019-06-04 11:54 ` Greg KH
2019-05-31 13:50 CKI Project
2019-05-31 14:17 ` Veronika Kabatova
2019-05-23  9:33 CKI Project
2019-05-23  9:40 ` Greg KH
2019-05-17  9:37 CKI Project
2019-05-14 17:54 CKI Project
2019-05-14 17:41 CKI Project
2019-05-13 13:22 CKI Project
2019-05-13 14:01 ` Veronika Kabatova
2019-05-13 15:01   ` Greg KH

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=2121614321.22097475.1558970115077.JavaMail.zimbra@redhat.com \
    --to=vkabatov@redhat.com \
    --cc=cki-project@redhat.com \
    --cc=jbastian@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).