From: Greg KH <gregkh@linuxfoundation.org>
To: Steven Rostedt <srostedt@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: ktest.pl always returns 0?
Date: Tue, 25 Sep 2012 11:00:28 -0700 [thread overview]
Message-ID: <20120925180028.GA22896@kroah.com> (raw)
Hi Steven,
I'm trying to use ktest to do build tests of the stable patch series to
verify I didn't mess anything up, but I'm finding that ktest always
returns 0 when finished, no matter if the build test was successful or
failed.
Is this right? Is there some other way to determine if ktest fails
other than greping the output log?
Oh, and any hints on kicking off a ktest process on a remote machine in
a "simple" way? I'm just using ssh to copy over a script that runs
there, wrapping ktest.pl up with other stuff, I didn't miss the fact
that ktest itself can run remotely already, did I?
thanks,
greg k-h
next reply other threads:[~2012-09-25 18:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 18:00 Greg KH [this message]
2012-09-25 18:15 ` ktest.pl always returns 0? Steven Rostedt
2012-09-25 19:40 ` Greg KH
2012-09-25 20:33 ` Steven Rostedt
2012-09-25 23:48 ` Steven Rostedt
2012-09-26 16:21 ` Greg KH
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=20120925180028.GA22896@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srostedt@redhat.com \
/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