kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dor Laor <dlaor@redhat.com>
To: Martin Bligh <mbligh@google.com>
Cc: sudhir kumar <smalikphy@gmail.com>,
	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, 08 Jul 2009 12:25:32 +0300	[thread overview]
Message-ID: <4A54660C.6090509@redhat.com> (raw)
In-Reply-To: <33307c790907072140i2a09f28dx3b7d6b217e31eeef@mail.gmail.com>

On 07/08/2009 07:40 AM, Martin Bligh wrote:
>> ATM I will suggest to merge the patches in and let get tested so that
>> we can collect failures/breakages if any.
>
> I am not keen on causing regressions, which we've risked doing every
> time we change LTP. I think we at least need to get a run on a non-virtualized
> machine with some recent kernel, and exclude the tests that fail every time.

We can use the reported results (impressive) as a base.
When more regressions are introduced, we can chop more tests

  reply	other threads:[~2009-07-08  9:25 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
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 [this message]
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=4A54660C.6090509@redhat.com \
    --to=dlaor@redhat.com \
    --cc=autotest@test.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=lmr@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).