public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Winchester <kjwinchester@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Automated Kernel Testing
Date: Sat, 02 Feb 2008 20:46:48 -0400	[thread overview]
Message-ID: <47A50EF8.6020507@gmail.com> (raw)


Hi Ingo & Andrew,

Since you both seem to be quite interested in the number of kernel
testers and the reporting of bugs, I figured I would bounce this idea
off of you...

As a part-time kernel tester, I find it interesting to see that Ingo has
tools that are able to automatically configure/build/boot/test kernels,
and it has given me the following ideas:

- For people like me, it would be great if there were a downloadable
collection of tools for performing similar testing on my box here
whenever I'm not using it.
- The tools could build a kernel, boot it, run some standard tests, and
report any problems automatically.
- The kernel oops web site and auto-submit tool seems like it would be a
very good companion to the testing tools (if you don't already have them
integrated).
- In the future, I would expect that a SETI@Home-style testing package
could be integrated into distribution repositories so that users could
do automatic testing (build testing for people scared about data loss,
and boot testing as well for those not worried).

I would be happy to help out with the work in developing this set of
tools (as far as my limited skills allow), but I have a feeling that you
already have most of it in some form.  I think the final piece is just
the integration and marketing so that the barrier to kernel testing gets
lowered considerably.

Does this seem like a reasonable idea, or is it something that you
already had in mind (that it just took me longer to see)?

-- 
Kevin Winchester

             reply	other threads:[~2008-02-03  0:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-03  0:46 Kevin Winchester [this message]
2008-02-08 17:07 ` Automated Kernel Testing Andi Kleen

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=47A50EF8.6020507@gmail.com \
    --to=kjwinchester@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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