All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: sudhir kumar <smalikphy@gmail.com>
Cc: Martin Bligh <mbligh@google.com>,
	Autotest mailing list <autotest@test.kernel.org>,
	Lucas Meneghel Rodrigues <mrodrigu@redhat.com>,
	Uri Lublin <uril@redhat.com>, kvm-devel <kvm@vger.kernel.org>
Subject: Re: [Autotest] [AUTOTEST] [PATCH 1/2] Add latest LTP test in autotest
Date: Tue, 7 Jul 2009 12:31:44 -0300	[thread overview]
Message-ID: <6ac58f4f0907070831h381a405bqdd58fdfaf132333e@mail.gmail.com> (raw)
In-Reply-To: <a50cf5ab0907070024g2b1519acudd0d1a6a21c630ea@mail.gmail.com>

On Tue, Jul 7, 2009 at 4:24 AM, sudhir kumar<smalikphy@gmail.com> wrote:
>> OK, Can we encapsulate this into the wrapper though, rather than making
>> people do it manually? in the existing ltp.patch or something?
>>
> definitely we can do that, but that needs to know about all the corner
> cases of failure. So may be we can continue enhancing the patch as per
> the failure reports on different OSes.

For the most immediate needs, we could try  building LTP with make -k.
Plain re-package of LTP kinda goes against our own rules. The
preferred way to do testsuite modifications is patching before the
execution. So let's strive to use the approach 'upstream package
unmodified, patch if needed'. That's how distro package does it, makes
sense for us too.

> 1 more thing I wanted to start a discussion on LTP mailing list is to
> make aware the testcase if it is running on a physical host or on a
> guest(say KVM guest). Testcases like power management, group
> scheduling fairness etc do not make much sense to run on a guest(as
> they will fail or break). So It is better for the test to recognise
> the environment and not execute if it is under virtualization and it
> is supposed to fail or break under that environment. Does that make
> sense to you also ?

We need to make an assessment of what we would expect to see failing
under a guest. LTP has a fairly large codebase, so it will be a fair
amount of work.

Lucas

  reply	other threads:[~2009-07-07 15:31 UTC|newest]

Thread overview: 19+ 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
2009-07-06 18:37   ` [Autotest] " Martin Bligh
2009-07-07  7:24     ` sudhir kumar
2009-07-07 15:31       ` Lucas Meneghel Rodrigues [this message]
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 10:19           ` [LTP] " Subrata Modak
2009-07-08 15:05           ` Martin Bligh
2009-07-08 15:05             ` [LTP] " Martin Bligh
2009-07-08 23:05           ` Mike Frysinger
2009-07-08 23:05             ` [LTP] " 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=6ac58f4f0907070831h381a405bqdd58fdfaf132333e@mail.gmail.com \
    --to=lmr@redhat.com \
    --cc=autotest@test.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=mbligh@google.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.