From: Subrata Modak <subrata@linux.vnet.ibm.com>
To: Garrett Cooper <yanegomi@gmail.com>
Cc: LTP Mailing List <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [PATCH 00/02] Integrate Valgrind Memory Check Tool to LTP
Date: Wed, 26 Aug 2009 12:41:19 +0530 [thread overview]
Message-ID: <1251270680.19240.4.camel@subratamodak.linux.ibm.com> (raw)
In-Reply-To: <364299f40908251909m7ed3e630r475500b21b16a54f@mail.gmail.com>
On Tue, 2009-08-25 at 19:09 -0700, Garrett Cooper wrote:
> On Tue, Aug 25, 2009 at 2:22 PM, Paul Larson<paul.larson@canonical.com> wrote:
> > Subrata Modak wrote:
> >
> >>> 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?
> >>
> >> But, creating another script say under testscripts will be to duplicate
> >> again runltp code, as the same script should be able to parse all the
> >> options what we use with runltp. So, keeping it in runltp will just a
> >> little overhead. And, may be we can introduce some longoptions or
> >> manpage for ltp as suggested by people earlier !!
> >
> > It doesn't need to have anywhere near the same options available as
> > under runltp. Other than being able to specify a set of tests to run, I
> > can't really think of a need for many of the others.
>
> Rather than make runltp into a huge long-options setup, why not
> separate out the common functionality in runltp into a library, make
Hmmm. I do not know how to do this. Can you show me. I can then try.
> it source-able from runltp, runltp-lite, and whatever script is used
> to call valgrind?
Till then, lets have this extended options in runltp.
Regards--
Subrata
> Thanks,
> -Garrett
------------------------------------------------------------------------------
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-26 7:11 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 ` [LTP] [PATCH 00/02] Integrate Valgrind Memory Check Tool to LTP Paul Larson
2009-08-25 10:12 ` Subrata Modak
2009-08-25 21:22 ` Paul Larson
2009-08-26 2:09 ` Garrett Cooper
2009-08-26 7:11 ` Subrata Modak [this message]
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=1251270680.19240.4.camel@subratamodak.linux.ibm.com \
--to=subrata@linux.vnet.ibm.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=yanegomi@gmail.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