ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] kernel testing standard
Date: Wed, 04 Jun 2014 22:51:24 +0900	[thread overview]
Message-ID: <538F245C.2090006@hitachi.com> (raw)
In-Reply-To: <20140530225321.GA20492@thunk.org>

(2014/05/31 7:53), Theodore Ts'o wrote:
> On Fri, May 30, 2014 at 02:35:30PM -0400, Steven Rostedt wrote:
>>
>> I agree with this. Just having a single place to put tests or tell
>> people where the tests are would be a huge improvement. If I wanted to
>> run my own tests on ext file systems, I should be able to set up the
>> same environment that Ted uses.
> 
> And you can!
> 
> 	https://git.kernel.org/cgit/fs/ext2/xfstests-bld.git/tree/README
> 
> My test environment has been designed so it's fully reproducible, and
> I've been pushing ext4 developers to use it before submitting me
> patches.  And if they don't, and I detect a problem which bisects back
> to one of their patches, I let them know gently that if they had used
> kvm-xfstests, they would have detected earlier.
> 
> Maybe just adding a field in the MAINTAINERS file which contains a
> pointer to the tests is the simplest solution?

Yes, I think at least that should be done. It is also good to know
what hardware is required to run the test for some subsystems.

And then, if we can share them among kernel developers, we can
step things forward to ensuring testing process in release/development
cycle. e.g. all subsystem maintainers run own tests before sending pull
request and right after rebasing kernel. This can ensures no regression
on that subsystem.

Thank you,

> 
>> If someone wants to run my ftrace tests, then they should be able to
>> as well (which I need to make available to the general
>> public). Better yet, this can open up a door for people to
>> contribute to new tests for a particular subsystem. I would love it
>> if people added tests for me to run on ftrace. I have a bunch of
>> hacks to test various functionality (as they are hacky, that's the
>> reason I haven't posted them yet).
> 
> Yeah, it took a while before I had done enough cleanup that I was
> willing to make thme fully public.  Now that I have, it's saved me a
> lot of time, most definitely.
> 
> 					- Ted
> 


-- 
Masami HIRAMATSU
Software Platform Research Dept. Linux Technology Research Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com

  reply	other threads:[~2014-06-04 13:51 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
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 [this message]
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=538F245C.2090006@hitachi.com \
    --to=masami.hiramatsu.pt@hitachi.com \
    --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