[LTP] Fw: LTP testcase analysis

[Pankaj Vinadrao Joshi]

Hi,
Hi,
I forgot to mention that  i am running LTP on  VM and i am getting error like  futex_wait and select tests are "$SYSCALL slept too long" and the test is getting failed because  vm is not getting CPU time as expected.
Is there any that i can configure or manage this cpu time related issue for now as i am running on slower machine the time constrain doesnt value for me...i just need test to be passed...is there any way to do so??
Kindly suggest.

Thanks!



________________________________________
From: Martin Doucha <mdoucha@suse.cz>
Sent: Tuesday, April 14, 2020 3:35 PM
To: Pankaj  Vinadrao Joshi
Cc: ltp@lists.linux.it
Subject: Re: [LTP] LTP testcase analysis

On 14. 04. 20 10:45, Pankaj Vinadrao Joshi wrote:
> Hi,
> i am running LTP on x86 with 5.4.3 kernel.i gave $ ./runltp command to
> run the complete LTP but found some failures,like
> oom01,futex_wait05,select04 etc.
>
> When i tried to run single test some of them turns into PASS which
> earlier got failed.like oom01 was failed then i gave coomand $./runltp
> -s oom01 and after that it got pass.
>
> why it could be happened,any specific reason,if you know please suggest??

The most common errors for futex_wait and select tests are "$SYSCALL
slept too long". These errors usually happen when you run the test in a
VM on overloaded host because the VM doesn't get enough CPU time to wake
the test process up within time limit.

OOM tests have issues in the mlock() test case. OOM killer is blocked by
mlock() which usually results in the parent shell being killed instead
of the expected OOM victim. This is a known kernel bug with some denial
of service potential but so far nobody came up with a fix that wouldn't
create memory corruption bugs.

That's all I can tell you without seeing the actual test output.

--
Martin Doucha   mdoucha@suse.cz
QA Engineer for Software Maintenance
SUSE LINUX, s.r.o.
CORSO IIa
Krizikova 148/34
186 00 Prague 8
Czech Republic
[EXT]
__________________________________________________________________________________________________

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linux.it/pipermail/ltp/attachments/20200414/0596af94/attachment.htm>