On Tue, Jul 7, 2009 at 12:07 AM, Martin Bligh<mbligh@xxxxxxxxxx> 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? > I have rebased the patches and updated the existing ltp.patch. I will be sending them soon. Also for runningn ltp under kvm I have generated a patch kvm_ltp.patch whose purpose is same as of ltp.patch but only for kvm guests. i will be sending the results of execution on the guest as well as on bare metal. Thanks everyone for your comments!! -- Sudhir Kumar -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
