From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: sudhir kumar <smalikphy@gmail.com>
Cc: Autotest mailing list <autotest@test.kernel.org>,
kvm-devel <kvm@vger.kernel.org>,
Lucas Meneghel Rodrigues <mrodrigu@redhat.com>,
Uri Lublin <uril@redhat.com>
Subject: Re: [AUTOTEST] [PATCH 1/2] Add latest LTP test in autotest
Date: Mon, 06 Jul 2009 03:58:39 -0300 [thread overview]
Message-ID: <1246863519.2865.18.camel@localhost.localdomain> (raw)
In-Reply-To: <a50cf5ab0907052240xf22b2b2rf7b90cc819d0ee87@mail.gmail.com>
On Mon, 2009-07-06 at 11:10 +0530, sudhir kumar wrote:
> This patch updates the ltp wrapper in autotest to execute the latest ltp.
> At present autotest contains ltp which is more than 1 year old. There have
> been added lots of testcases in ltp within this period. So this patch updates
> the wrapper to run the June2009 release of ltp which is available at
> http://prdownloads.sourceforge.net/ltp/ltp-full-20090630.tgz
Indeed it would be a good time to update the LTP version being used on
autotest.
> Issues: LTP has a history of some of the testcases getting broken. Anyways
> that has nothing to worry about with respect to autotest. One of the known issue
> is broken memory controller issue with latest kernels(cgroups and memory
> resource controller enabled kernels). The workaround for them I use is to
> disable or delete those tests from ltp source and tar it again with the same
> name. Though people might use different workarounds for it.
A good start would be LTP build being more failure resilent (ie, if one
particular test fails to compile, don't fail the whole build). I will
raise this question on the LTP mailing list.
> I have added an option which generates a fancy html results file. Also the
> run is left to be a default run as expected.
>
> For autotest users, please untar the results file I am sending, run
> cd results/default; firefox results.html, click ltp_results.html
> This is a symlink to the ltp_results.html which is generated by ltp.
>
> Please provide your comments, concerns and issues.
>
> Signed-off-by: Sudhir Kumar <skumar@linux.vnet.ibm.com>
>
> Index: autotest/client/tests/ltp/ltp.py
> ===================================================================
> --- autotest.orig/client/tests/ltp/ltp.py
> +++ autotest/client/tests/ltp/ltp.py
> @@ -23,8 +23,8 @@ class ltp(test.test):
> self.job.require_gcc()
>
>
> - # http://prdownloads.sourceforge.net/ltp/ltp-full-20080229.tgz
> - def setup(self, tarball = 'ltp-full-20080229.tar.bz2'):
> + # http://prdownloads.sourceforge.net/ltp/ltp-full-20090630.tgz
> + def setup(self, tarball = 'ltp-full-20090630.tgz'):
> tarball = utils.unmap_url(self.bindir, tarball, self.tmpdir)
> utils.extract_tarball_to_dir(tarball, self.srcdir)
> os.chdir(self.srcdir)
> @@ -52,8 +52,9 @@ class ltp(test.test):
> # In case the user wants to run another test script
> if script == 'runltp':
> logfile = os.path.join(self.resultsdir, 'ltp.log')
> + htmlfile = os.path.join(self.resultsdir, 'ltp_results.html')
> failcmdfile = os.path.join(self.debugdir, 'failcmdfile')
> - args2 = '-q -l %s -C %s -d %s' % (logfile, failcmdfile,
> self.tmpdir)
> + args2 = '-l %s -g %s -C %s -d %s' % (logfile, htmlfile,
> failcmdfile, self.tmpdir)
> args = args + ' ' + args2
>
> cmd = os.path.join(self.srcdir, script) + ' ' + args
Patch looks good to me.
next prev parent reply other threads:[~2009-07-06 6:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 5:40 [AUTOTEST] [PATCH 1/2] Add latest LTP test in autotest sudhir kumar
2009-07-06 6:58 ` Lucas Meneghel Rodrigues [this message]
2009-07-06 18:37 ` [Autotest] " Martin Bligh
2009-07-07 7:24 ` sudhir kumar
2009-07-07 15:31 ` Lucas Meneghel Rodrigues
2009-07-08 4:22 ` sudhir kumar
2009-07-08 4:40 ` Martin Bligh
2009-07-08 9:25 ` Dor Laor
2009-07-08 9:30 ` sudhir kumar
2009-07-07 17:45 ` Martin Bligh
2009-07-08 4:17 ` sudhir kumar
2009-07-08 10:19 ` Subrata Modak
2009-07-08 10:19 ` Subrata Modak
2009-07-08 15:05 ` Martin Bligh
2009-07-08 23:05 ` Mike Frysinger
2009-07-13 4:45 ` [Autotest] [AUTOTEST] " sudhir kumar
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=1246863519.2865.18.camel@localhost.localdomain \
--to=lmr@redhat.com \
--cc=autotest@test.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=mrodrigu@redhat.com \
--cc=smalikphy@gmail.com \
--cc=uril@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