From: Martin Bligh <mbligh@google.com>
To: sudhir kumar <smalikphy@gmail.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: Tue, 7 Jul 2009 21:40:04 -0700 [thread overview]
Message-ID: <33307c790907072140i2a09f28dx3b7d6b217e31eeef@mail.gmail.com> (raw)
In-Reply-To: <a50cf5ab0907072122k6bd4fc89i4776f9d71a2574fb@mail.gmail.com>
> 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.
next prev parent reply other threads:[~2009-07-08 4:40 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 [this message]
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 ` [LTP] " Subrata Modak
2009-07-08 10:19 ` Subrata Modak
2009-07-08 15:05 ` [LTP] " Martin Bligh
2009-07-08 15:05 ` Martin Bligh
2009-07-08 23:05 ` [LTP] " Mike Frysinger
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=33307c790907072140i2a09f28dx3b7d6b217e31eeef@mail.gmail.com \
--to=mbligh@google.com \
--cc=autotest@test.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=lmr@redhat.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.