[LTP] LTP msgstress03, msgstress04 failure on linux 5.10.19 and 5.10.22

[Pankaj Vinodrao Joshi]

sorry, i forgot to attach log file.The LTP version i am using is  LTP Version:  20200515 and even i have tried with latest master sources as well


Thanks
________________________________
From: Cyril Hrubis <chrubis@suse.cz>
Sent: Thursday, April 8, 2021 2:57 PM
To: Pankaj Vinodrao Joshi <Pankaj.VJ@exaleapsemi.com>
Cc: ltp@lists.linux.it <ltp@lists.linux.it>
Subject: Re: [LTP] LTP msgstress03, msgstress04 failure on linux 5.10.19 and 5.10.22

Hi!
> I am running msgstress03,msgstress04 with 5.10.19 and 5.10.22 custom
> kernel built using Yocto but both test are getting failed repeatedly.
> i am not able to understand what making both test to fail since these
> tests are stress tests for message queue want to figure if anything
> going wrong with message queue.

What about the LTP version? Can you please include that information
every time you ask abou test failures?

> Pasting few error messages and attaching detailed logs of failures
>
> msgstress03:-
> msgsnd() error in child 9458, write # = 10000, key = 65e2d9c4: Interrupted system call
> msgstress03    1  TBROK  :  tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43902).
> msgstress03    2  TBROK  :  tst_sig.c:232: Remaining cases broken
> msgstress03    1  TBROK  :  tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43925).
> msgstress03    2  TBROK  :  tst_sig.c:232: Remaining cases broken
> msgstress03    0  TWARN  :  tst_tmpdir.c:336: tst_rmdir: rmobj(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed: Cannot open directory /tmp/ltp-9Raz9tykpq/msgQaAD8i; errno=2: ENOENT
> msgstress03    1  TBROK  :  tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43927).
> msgstress03    2  TBROK  :  tst_sig.c:232: Remaining cases broken
> msgstress03    0  TWARN  :  tst_tmpdir.c:336: tst_rmdir: rmobj(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed: Cannot open directory /tmp/ltp-9Raz9tykpq/msgQaAD8i; errno=2: ENOENT
> msgsnd() error in child 9468, write # = 10000, key = 5364a4ac: Interrupted system call
> msgstress03    1  TBROK  :  tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43918).
> msgstress03    2  TBROK  :  tst_sig.c:232: Remaining cases broken
> msgstress03    0  TWARN  :  tst_tmpdir.c:336: tst_rmdir: rmobj(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed: unlink(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed; errno=2: ENOENT
> msgsnd() error in child 9450, write # = 10000, key = 6015ef48: Interrupted system call
> msgstress03    1  TBROK  :  tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43883).
> msgstress03    2  TBROK  :  tst_sig.c:232: Remaining cases broken
> msgstress03    0  TWARN  :  tst_tmpdir.c:336: tst_rmdir: rmobj(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed: unlink(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed; errno=2: ENOENT
> msgstress03    1  TBROK  :  tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43924).
> msgstress03    2  TBROK  :  tst_sig.c:232: Remaining cases broken
> msgstress03    0  TWARN  :  tst_tmpdir.c:336: tst_rmdir: rmobj(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed: unlink(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed; errno=2: ENOENT
> msgsnd() error in child 9454, write # = 10000, key = 37efb13a: Interrupted system call

This looks like fallout from the test doing unclean exit, the root cause
for the failure should be somewhere at the beginning of the log.

--
Cyril Hrubis
chrubis@suse.cz
[EXT]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linux.it/pipermail/ltp/attachments/20210408/68863712/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: msgstress03
Type: application/octet-stream
Size: 56955 bytes
Desc: msgstress03
URL: <http://lists.linux.it/pipermail/ltp/attachments/20210408/68863712/attachment-0001.obj>