From: James Takahashi <takahash@us.ibm.com>
To: LTP list <ltp-list@lists.sourceforge.net>
Cc: "iranna.ankad" <iranna.ankad@in.ibm.com>, takahash <takahash@us.ibm.com>
Subject: Re: [LTP] [RFC] Remove testcases/pounder21
Date: Wed, 17 Nov 2010 17:43:03 -0800 [thread overview]
Message-ID: <20101118014303.GA30825@us.ibm.com> (raw)
In-Reply-To: <1289458673.5622.19.camel@subratamodak.linux.ibm.com>
> > On Wed, Nov 10, 2010 at 12:53 PM, Murlin Wenzel <mwenzel@novell.com> wrote:
> >
> > Answering my own question:
> > http://www.mail-archive.com/ltp-list@lists.sourceforge.net/msg09788.html
> > , I asked this earlier on this year and someone replied saying "don't
> > remove it". If it's not removed and serves a particular purpose, maybe
> > it should be moved to a different section of the tree to avoid
> > confusion in the future (in particular if it's a framework and not
> > actually a test / test suite).
Yeah, that was me.
I now understand that the LTP Makefile reorganization from earlier in
the year attempts to recursively build everything that lives under
'testcases' due to the (reasonable) assumption that everything in
'testcases' is a subtest to be executed under LTP control.
'pounder', however, is not a subtest to be executed under LTP control.
It is a separate test execution framework, and in fact, executes LTP's
'runltp' as a subtest within that framework. This allows us to run
other standalone tests, test suites, and/or benchmarks along side LTP.
I agree that it would make sense to move pounder21 to some other place
in the tree. At first glance, 'utils' looks like a reasonable spot.
Thoughts?
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2010-11-18 1:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-08 21:57 [LTP] [RFC] Remove testcases/pounder21 Garrett Cooper
2010-11-10 20:28 ` Garrett Cooper
2010-11-10 20:53 ` Murlin Wenzel
2010-11-11 0:54 ` Garrett Cooper
2010-11-11 6:57 ` Subrata Modak
2010-11-11 8:47 ` Iranna D Ankad
[not found] ` <OF7E98D2D1.7AEC88E3-ON652577D8.002CB466-652577D8.0030671A@LocalDomain>
2010-11-11 10:23 ` Shubham Goyal
2010-11-11 17:18 ` Garrett Cooper
2010-11-12 10:41 ` Subrata Modak
2010-11-12 10:48 ` Shubham Goyal
2010-11-18 1:43 ` James Takahashi [this message]
2010-11-18 7:12 ` Garrett Cooper
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=20101118014303.GA30825@us.ibm.com \
--to=takahash@us.ibm.com \
--cc=iranna.ankad@in.ibm.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