ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: chrubis@suse.cz, James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [CORE TOPIC] kernel testing standard
Date: Mon, 09 Jun 2014 19:54:11 +0200	[thread overview]
Message-ID: <5395F4C3.80005@gmail.com> (raw)
In-Reply-To: <20140609144415.GA3947@rei>

On 06/09/2014 04:44 PM, chrubis@suse.cz wrote:
> Hi!
>>> Is there a reason not to run the latest version of LTP (unless bisecting
>>> LTP ;-)? The syscall API is supposed to be stable.
>>
>> I think not, and we have strong reasons for wanting to run the latest
>> LTP against every kernel (including stable ones), not just the version
>> in the test directory, so in practise, it looks like this doesn't meet
>> the changes with the kernel test for inclusion.  On the other hand,
>> having the tests available is also useful.   Perhaps we just need a
>> tests repo which pulls from all our other disparate tests so there's one
>> location everyone knows to go for the latest?
> 
> That sounds good to me. But as allready said, creating some
> scripts/repos that pulls and runs all the tests is relatively easy.
> Creating configurations and figuring out who needs to run which parts is
> not.
> 
> I think that the main problem here is the communication and information
> sharing. Maybe we can start with a wiki page or a similar document that
> summarizes maintained testsuites, their purpose and structure. Because
> just now, if there is any information about kernel testing, it is
> scattered around the web, forums, etc.
> 
> Also I would like to see more communication between the Kernel and QA.
> 
> It's getting a bit better as we have linux-api mailing list and (thanks
> to Michaal Kerrisk) commits that change kernel API are starting to CC
> it. Which I consider as a great improvement because now we at least know
> what we need to write tests for. However I still think that there is
> some work lost in the process, particulary because the kernel devs who
> wrote the userspace API have surely implemented some kind of tests for
                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Actually, I can point to numerous examples that show that this sadly
could not have been the case. Very many times I've written tests for
an API, or some API feature, only to discover that the most basic of
tests fails--in other words, clearly no-on--including the kernel
dev--did any testing of that particular feature before me.

Cheers,

Michael


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

  reply	other threads:[~2014-06-09 17:54 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
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) [this message]
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=5395F4C3.80005@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=chrubis@suse.cz \
    --cc=ksummit-discuss@lists.linuxfoundation.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