On Tue, Jul 7, 2009 at 12:07 AM, Martin Blighmbl...@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
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
On Wed, Jul 8, 2009 at 2:55 PM, Dor Laordl...@redhat.com wrote:
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
On Wed, 2009-07-08 at 09:47 +0530, sudhir kumar wrote:
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
On Tue, Jul 7, 2009 at 12:07 AM, Martin Blighmbl...@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
On Tue, Jul 7, 2009 at 4:24 AM, sudhir kumarsmalik...@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
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
On Tue, Jul 7, 2009 at 9:01 PM, Lucas Meneghel Rodriguesl...@redhat.com wrote:
On Tue, Jul 7, 2009 at 4:24 AM, sudhir kumarsmalik...@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?
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,
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
10 matches
Mail list logo
