stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Veronika Kabatova <vkabatov@redhat.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: CKI Project <cki-project@redhat.com>,
	Linux Stable maillist <stable@vger.kernel.org>
Subject: Re: ✅ PASS: Stable queue: queue-5.0
Date: Tue, 7 May 2019 13:56:34 -0400 (EDT)	[thread overview]
Message-ID: <870847532.18462136.1557251794376.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20190507170150.GA1468@kroah.com>



----- 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/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#distribution/ltp/lite
> >     [3]:
> >     https://github.com/CKI-project/tests-beaker/archive/master.zip#filesystems/loopdev/sanity
> >     [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/driver/sanity
> >     [6]:
> >     https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/httpd/mod_ssl-smoke
> >     [7]:
> >     https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/iotop/sanity
> >     [8]:
> >     https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/tuned/tune-processes-through-perf
> >     [9]:
> >     https://github.com/CKI-project/tests-beaker/archive/master.zip#standards/usex/1.9-29
> >     [10]:
> >     https://github.com/CKI-project/tests-beaker/archive/master.zip#storage/lvm/thinp/sanity
> >     [11]:
> >     https://github.com/CKI-project/tests-beaker/archive/master.zip#/packages/selinux-policy/serge-testsuite
> >     [12]:
> >     https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/audit/audit-testsuite
> >     [13]:
> >     https://github.com/CKI-project/tests-beaker/archive/master.zip#stress/stress-ng
> 
> 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/xfstests/RUNTESTS
[1] https://github.com/CKI-project/tests-beaker/blob/master/filesystems/xfs/xfstests/known_issues

> thanks,
> 
> greg k-h
> 
> 

  reply	other threads:[~2019-05-07 17:56 UTC|newest]

Thread overview: 79+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-07 15:21 ✅ PASS: Stable queue: queue-5.0 CKI Project
2019-05-07 17:01 ` Greg KH
2019-05-07 17:56   ` Veronika Kabatova [this message]
2019-05-08  9:24     ` Greg KH
2019-05-08 16:22       ` Don Zickus
2019-05-08 16:52         ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2019-05-09 11:16 CKI Project
2019-05-09  3:25 CKI Project
2019-05-08 23:33 CKI Project
2019-05-08 15:54 CKI Project
2019-05-08 16:49 ` Greg KH
2019-05-08 19:59   ` Major Hayden
2019-05-09  0:27     ` Sasha Levin
2019-05-09  6:49     ` Greg KH
2019-05-09 12:10       ` Major Hayden
2019-05-08  8:46 CKI Project
2019-05-06 16:26 CKI Project
2019-05-06  9:26 CKI Project
2019-05-05 15:31 CKI Project
2019-05-05 15:05 CKI Project
2019-05-04 11:28 CKI Project
2019-05-04  9:27 CKI Project
2019-05-02 16:30 CKI Project
2019-05-02 11:49 CKI Project
2019-05-02  9:56 CKI Project
2019-04-30  1:05 CKI Project
2019-04-29 10:32 CKI Project
2019-04-27 17:35 CKI Project
2019-04-25 12:42 CKI Project
2019-04-24 17:09 CKI Project
2019-04-24  5:01 CKI Project
2019-04-24  1:04 CKI Project
2019-04-23 20:59 CKI Project
2019-04-15 21:33 CKI Project
2019-04-15 18:03 CKI Project
2019-04-15 16:47 CKI Project
2019-04-15 16:18 CKI Project
2019-04-15 15:42 CKI Project
2019-04-15 11:03 CKI Project
2019-04-11 22:15 CKI Project
2019-04-10 19:15 CKI Project
2019-04-10  4:05 CKI Project
2019-04-04 14:06 CKI Project
2019-04-04 12:34 CKI Project
2019-04-01 14:42 CKI Project
2019-04-01 14:24 CKI Project
2019-03-31  1:03 CKI Project
2019-03-31  0:21 CKI Project
2019-03-30 23:38 CKI Project
2019-03-30 14:28 CKI Project
2019-03-30 13:59 CKI Project
2019-03-30  2:26 CKI Project
2019-03-29 17:14 CKI Project
2019-03-29  8:39 CKI Project
2019-03-29  8:00 CKI Project
2019-03-28 22:56 CKI Project
2019-03-27 20:13 CKI Project
2019-03-27 19:58 CKI Project
2019-03-26 11:44 CKI Project
2019-03-26  4:05 CKI Project
2019-03-26  3:03 CKI Project
2019-03-24 23:24 CKI Project
2019-03-22 17:54 CKI Project
2019-03-22  7:49 CKI Project
2019-03-22  4:25 CKI Project
2019-03-22  4:03 CKI Project
2019-03-22  3:59 CKI Project
2019-03-22  3:46 CKI Project
2019-03-21 18:34 CKI Project
2019-03-21 15:57 CKI Project
2019-03-19  0:35 CKI Project
2019-03-12 20:34 CKI Project
2019-03-12 19:38 CKI Project
2019-03-12 14:26 CKI Project
2019-03-12 13:37 CKI Project
2019-03-12  4:20 CKI Project
2019-03-11 23:34 CKI Project
2019-03-11  4:44 CKI Project
2019-03-08 22:07 CKI

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=870847532.18462136.1557251794376.JavaMail.zimbra@redhat.com \
    --to=vkabatov@redhat.com \
    --cc=cki-project@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --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).