All of lore.kernel.org
 help / color / mirror / Atom feed
From: Major Hayden <major@redhat.com>
To: Linux Stable maillist <stable@vger.kernel.org>
Subject: Re: ❎ FAIL: Stable queue: queue-5.0
Date: Tue, 30 Apr 2019 07:35:45 -0500	[thread overview]
Message-ID: <efa70f6a-8854-7494-81a6-f729aeca5351@redhat.com> (raw)
In-Reply-To: <cki.6C208109D9.WGQF5P41NS@redhat.com>

On 4/30/19 7:32 AM, CKI Project wrote:
>   aarch64:
>      ✅ Boot test [0]
>      ❎ LTP lite [1]
>      ✅ Loopdev Sanity [2]
>      ✅ AMTU (Abstract Machine Test Utility) [3]
>      ✅ Ethernet drivers sanity [4]
>      ✅ httpd: mod_ssl smoke sanity [5]
>      ✅ iotop: sanity [6]
>      ✅ tuned: tune-processes-through-perf [7]
>      ✅ Usex - version 1.9-29 [8]
>      ✅ lvm thinp sanity [9]
>      ✅ Boot test [0]
>      ✅ xfstests: ext4 [10]
>      ✅ xfstests: xfs [10]
>      🚧 ✅ Networking route: pmtu [11]
>      🚧 ✅ audit: audit testsuite test [12]
>      🚧 ✅ stress: stress-ng [13]

All of the tests look fine for this build, but the aarch64 test failed on mtest06 in LTP:

> <<<test_start>>>
> tag=mtest06 stime=1556617569
> cmdline="  mmap1"
> contacts=""
> analysis=exit
> <<<test_output>>>
> tst_test.c:1085: INFO: Timeout per run is 0h 05m 00s
> tst_test.c:1085: INFO: Timeout per run is 0h 03m 00s
> mmap1.c:234: INFO: [3] mapped: 20000, sigsegv hit: 2864, threads spawned: 8
> mmap1.c:237: INFO: [3] repeated_reads: 0, data_matched: 17590074
> mmap1.c:234: INFO: [6] mapped: 50000, sigsegv hit: 5296, threads spawned: 20
> mmap1.c:237: INFO: [6] repeated_reads: 322, data_matched: 45330029
> Test timeouted, sending SIGKILL!
> tst_test.c:1125: INFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1
> tst_test.c:1126: BROK: Test killed! (timeout?)
>  
> Summary:
> passed   0
> failed   0
> skipped  0
> warnings 0
> <<<execution_status>>>
> initiation_status="ok"
> duration=180 termination_type=exited termination_id=2 corefile=no
> cutime=984 cstime=17098
> <<<test_end>>>

This could be due to a slow host on our side and we're still taking a look. I figured that sharing all of the results would be helpful while we investigate. :)

--
Major Hayden

  reply	other threads:[~2019-04-30 12:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-30 12:32 ❎ FAIL: Stable queue: queue-5.0 CKI Project
2019-04-30 12:35 ` Major Hayden [this message]
2019-04-30 13:03   ` Sasha Levin
2019-04-30 13:27     ` Greg KH
2019-04-30 13:41       ` Sasha Levin
2019-04-30 14:01         ` Greg KH
2019-04-30 15:17           ` Major Hayden
2019-04-30 15:58             ` Sasha Levin
2019-04-30 18:44               ` Sven Joachim
  -- strict thread matches above, loose matches on Subject: below --
2019-05-06 11:16 CKI Project
2019-05-06 11:26 ` Veronika Kabatova
2019-05-06 12:36   ` Greg KH
2019-05-02 12:32 CKI Project
2019-05-02 12:39 ` Major Hayden
2019-05-02 14:08   ` Greg KH
2019-04-29 13:36 CKI Project
2019-04-29 12:50 CKI Project
2019-04-29 12:38 CKI Project
2019-04-29 12:42 ` Major Hayden
2019-04-29 13:10   ` Greg KH
2019-04-29 12:37 CKI Project
2019-04-04 18:00 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=efa70f6a-8854-7494-81a6-f729aeca5351@redhat.com \
    --to=major@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.