From: Andrew Jones <drjones@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [KTEST PATCH 00/10] collection of ktest patches
Date: Fri, 12 Aug 2011 20:03:36 +0200 [thread overview]
Message-ID: <20110812180336.GB18363@turtle.usersys.redhat.com> (raw)
In-Reply-To: <1313171058.18583.347.camel@gandalf.stny.rr.com>
On Fri, Aug 12, 2011 at 01:44:18PM -0400, Steven Rostedt wrote:
> On Fri, 2011-08-12 at 15:32 +0200, Andrew Jones wrote:
> > More than once I've had to drive git-bisect to bisect boot issues for
> > Xen guests. The last time I needed to do so I decided to give ktest a
> > whirl. While whirling I wrote a couple patches and added a few features.
> > This patchset is the collection.
>
> I do like your changes and I'll start queuing them up soon. Probably
> need to rename the PASS_COUNT though. What do you think of RERUN?
Thanks! I've sent the rerun patch.
>
> Anyway, I only post to Linus during the merge window (except for bug
> fixes), which means they wont be in mainline until 3.2.
>
no problem
> The best thing about this patchset, is that it proves that ktest is used
> by more than 1 person. It's doubled its usage statistics!
lol
>
> -- Steve
>
> >
> > Andrew Jones (10):
> > ktest: create outputdir, if it doesn't exist
> > ktest: small cleanup
> > ktest: factor reboot code
> > ktest: Introduce RESET_TIME
> > ktest: refactor monitor/boot/test code
> > ktest: make start_monitor_and_boot true to its name
> > ktest: Introduce PASS_COUNT
> > ktest: test faster, put REBOOT_ON_SUCCESS to more work
> > ktest: test faster, favor rsync over the tarball method
> > ktest: Introduce FAILURE_LINE
> >
> > tools/testing/ktest/ktest.pl | 208 +++++++++++++++++++++++----------------
> > tools/testing/ktest/sample.conf | 23 ++++-
> > 2 files changed, 147 insertions(+), 84 deletions(-)
> >
>
>
prev parent reply other threads:[~2011-08-12 18:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 13:32 Andrew Jones
2011-08-12 13:32 ` [PATCH 01/10] ktest: create outputdir, if it doesn't exist Andrew Jones
2011-08-12 13:32 ` [PATCH 02/10] ktest: small cleanup Andrew Jones
2011-08-12 13:32 ` [PATCH 03/10] ktest: factor reboot code Andrew Jones
2011-08-12 13:32 ` [PATCH 04/10] ktest: Introduce RESET_TIME Andrew Jones
2011-08-12 15:59 ` Steven Rostedt
2011-08-12 16:25 ` [PATCH 04/10 v2] ktest: Introduce CONSOLE_RESET_TIME Andrew Jones
2011-08-18 21:28 ` Steven Rostedt
2011-08-24 8:45 ` Andrew Jones
2011-08-12 13:32 ` [PATCH 05/10] ktest: refactor monitor/boot/test code Andrew Jones
2011-08-12 13:32 ` [PATCH 06/10] ktest: make start_monitor_and_boot true to its name Andrew Jones
2011-08-12 13:32 ` [PATCH 07/10] ktest: Introduce PASS_COUNT Andrew Jones
2011-08-12 16:49 ` Steven Rostedt
2011-08-12 17:09 ` Andrew Jones
2011-08-12 17:20 ` Steven Rostedt
2011-08-12 17:58 ` [PATCH 07/10 v2] ktest: Introduce RERUN Andrew Jones
2011-08-12 13:32 ` [PATCH 08/10] ktest: test faster, put REBOOT_ON_SUCCESS to more work Andrew Jones
2011-08-12 13:32 ` [PATCH 09/10] ktest: test faster, favor rsync over the tarball method Andrew Jones
2011-08-12 13:32 ` [PATCH 10/10] ktest: Introduce FAILURE_LINE Andrew Jones
2011-08-12 17:03 ` Steven Rostedt
2011-08-12 17:37 ` [PATCH 10/10 v2] " Andrew Jones
2011-08-12 17:44 ` [KTEST PATCH 00/10] collection of ktest patches Steven Rostedt
2011-08-12 18:03 ` Andrew Jones [this message]
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=20110812180336.GB18363@turtle.usersys.redhat.com \
--to=drjones@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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
Powered by JetHome