From: Paul Larson <paul.larson@canonical.com>
To: LTP Mailing List <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [PATCH 00/02] Integrate Valgrind Memory Check Tool to LTP
Date: Mon, 24 Aug 2009 07:47:12 -0500 [thread overview]
Message-ID: <4A928BD0.4000508@canonical.com> (raw)
In-Reply-To: <20090824093204.31997.18175.sendpatchset@subratamodak.linux.ibm.com>
Subrata Modak wrote:
> ./runltp -f <your-command-file> -M [1,2,3]
Due to runltp already becoming fairly bloated, and the fact that this is
really just to "test the tests", would it make sense to put it under
/scratch or /testscripts as a separate script, rather than just include
it as yet-another-option for runltp?
Thanks,
Paul Larson
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2009-08-24 12:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-24 9:32 [LTP] [PATCH 00/02] Integrate Valgrind Memory Check Tool to LTP Subrata Modak
2009-08-24 9:32 ` [LTP] [PATCH 01/02] Create the necessary Interface with runltp Subrata Modak
2009-08-24 9:32 ` [LTP] [PATCH 02/02] Script that will actually create the COMMAND File entries Subrata Modak
2009-08-24 9:33 ` [LTP] [RESULTS] The Actual results of the tests run with the new interface Subrata Modak
2009-08-24 12:47 ` Paul Larson [this message]
2009-08-25 10:12 ` [LTP] [PATCH 00/02] Integrate Valgrind Memory Check Tool to LTP Subrata Modak
2009-08-25 21:22 ` Paul Larson
2009-08-26 2:09 ` Garrett Cooper
2009-08-26 7:11 ` Subrata Modak
2009-08-26 7:11 ` Subrata Modak
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=4A928BD0.4000508@canonical.com \
--to=paul.larson@canonical.com \
--cc=ltp-list@lists.sourceforge.net \
/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