All of lore.kernel.org
 help / color / mirror / Atom feed
From: sudhir kumar <smalikphy@gmail.com>
To: Martin Bligh <mbligh@google.com>
Cc: Lucas Meneghel Rodrigues <lmr@redhat.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: Wed, 8 Jul 2009 09:47:52 +0530	[thread overview]
Message-ID: <a50cf5ab0907072117t7773ed87nde2b1811f95cb33e@mail.gmail.com> (raw)
In-Reply-To: <33307c790907071045v72e19614i571c36ad8af8062c@mail.gmail.com>

Ok Then. So my idea is to include the patch in autotest and let the
people report failures(in compilation or execution), and we can patch
autotest to apply the fix patch and build and run ltp. I do not think
we can find all cases untill and unless we start execution.

However I will start the discussion on the ltp list and see the
response from people. At least we can get the new testcases to be
aware of virtualization.

On Tue, Jul 7, 2009 at 11:15 PM, Martin Bligh<mbligh@google.com> wrote:
> On Tue, Jul 7, 2009 at 12:24 AM, sudhir kumar<smalikphy@gmail.com> wrote:
>> On Tue, Jul 7, 2009 at 12:07 AM, Martin Bligh<mbligh@google.com> wrote:
>>>>> Issues: LTP has a history of some of the testcases getting broken.
>>>
>>> Right, that's always the concern with doing this.
>>>
>>>>> 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.
>>>
>>> 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.
>>
>> 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 ?
>
> Yup, we can pass an excluded test list. I really wish they'd fix their
> tests, but I've been saying that for 6 years now, and it hasn't happened
> yet ;-(
>



-- 
Sudhir Kumar

  reply	other threads:[~2009-07-08  4:17 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
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 [this message]
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=a50cf5ab0907072117t7773ed87nde2b1811f95cb33e@mail.gmail.com \
    --to=smalikphy@gmail.com \
    --cc=autotest@test.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=lmr@redhat.com \
    --cc=mbligh@google.com \
    --cc=mrodrigu@redhat.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.