ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Theodore Ts'o <tytso@mit.edu>,
	"Justin M. Forbes" <jforbes@fedoraproject.org>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] kernel testing standard
Date: Fri, 23 May 2014 18:15:08 -0700	[thread overview]
Message-ID: <537FF29C.10301@roeck-us.net> (raw)
In-Reply-To: <20140524003036.GB26422@thunk.org>

On 05/23/2014 05:30 PM, Theodore Ts'o wrote:
> On Fri, May 23, 2014 at 09:05:02AM -0500, Justin M. Forbes wrote:
>> All good suggestions. As nice as it would be if tests were in tree, this
>> might be unmanageable. But even out of tree tests could be automatically
>> brought in provided they are listed somewhere in tree.  Ideally you
>> would be able to "make tests" and get all in tree tests run, or "make
>> alltests" and have it grab/build/run out of tree tests with git urls as
>> well.
>
> Um.... how long do you expect "make alltests" to run?
>
> And how do you deal with tests that require specific hardware?
>
> For ext4, just doing a light smoke test takes about 30 minutes.  For
> me to run the full set of tests using multiple file system
> configurations, it takes about 12 to 16 hours.  And that's just for
> one file system.  (I do the tests using KVM, with a 90 megabyte
> compressed root file system, and 55 gigabytes worth of scratch
> partitions.)
>

Guess that all depends on the scope of tests needed or wanted.
For my part (basic sanity testing of upcoming -stable releases),
where I boot images for various architectures in qemu, no more
than 10-15 minutes per image with a quad-core cpu.

Guenter

  reply	other threads:[~2014-05-24  1:15 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-23 11:47 Masami Hiramatsu
2014-05-23 13:32 ` Jason Cooper
2014-05-23 16:24   ` Olof Johansson
2014-05-23 16:35     ` Guenter Roeck
2014-05-23 16:36     ` Jason Cooper
2014-05-23 18:10     ` Masami Hiramatsu
2014-05-23 18:36       ` Jason Cooper
2014-05-23 18:06   ` Masami Hiramatsu
2014-05-23 18:32     ` Jason Cooper
2014-05-23 14:05 ` Justin M. Forbes
2014-05-23 16:04   ` Mark Brown
2014-05-24  0:30   ` Theodore Ts'o
2014-05-24  1:15     ` Guenter Roeck [this message]
2014-05-26 11:33     ` Masami Hiramatsu
2014-05-30 18:35       ` Steven Rostedt
2014-05-30 20:59         ` Kees Cook
2014-05-30 22:53         ` Theodore Ts'o
2014-06-04 13:51           ` Masami Hiramatsu
2014-05-26 17:08     ` Daniel Vetter
2014-05-26 18:21       ` Mark Brown
2014-05-28 15:37 ` Mel Gorman
2014-05-28 18:57   ` Greg KH
2014-05-30 12:07     ` Linus Walleij
2014-06-05  0:23       ` Greg KH
2014-06-05  6:54         ` Mel Gorman
2014-06-05  8:30           ` Geert Uytterhoeven
2014-06-05  8:44             ` chrubis
2014-06-05  8:53             ` Daniel Vetter
2014-06-05 11:17               ` Masami Hiramatsu
2014-06-05 11:58                 ` Daniel Vetter
2014-06-06  9:10                   ` Masami Hiramatsu
2014-06-05 14:10             ` James Bottomley
2014-06-06  9:17               ` Masami Hiramatsu
2014-06-09 14:44               ` chrubis
2014-06-09 17:54                 ` Michael Kerrisk (man-pages)
2014-06-05  8:39           ` chrubis

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=537FF29C.10301@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=jforbes@fedoraproject.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=tytso@mit.edu \
    /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