From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] LTP msgstress03, msgstress04 failure on linux 5.10.19 and 5.10.22
Date: Thu, 8 Apr 2021 11:27:09 +0200 [thread overview]
Message-ID: <YG7Mbc/ZTnD85SAh@yuki> (raw)
In-Reply-To: <BM1PR01MB2868C0458678E57C87BBC708EE749@BM1PR01MB2868.INDPRD01.PROD.OUTLOOK.COM>
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
next prev parent reply other threads:[~2021-04-08 9:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 9:07 [LTP] msgstress03, msgstress04 failure on linux 5.10.19 and 5.10.22 Pankaj Vinodrao Joshi
2021-03-29 9:26 ` xuyang2018.jy
2021-03-29 12:40 ` Pankaj Vinodrao Joshi
2021-04-08 9:02 ` [LTP] LTP " Pankaj Vinodrao Joshi
2021-04-08 9:27 ` Cyril Hrubis [this message]
2021-04-08 9:38 ` Pankaj Vinodrao Joshi
2021-04-08 10:28 ` Cyril Hrubis
2021-04-12 5:18 ` Pankaj Vinodrao Joshi
2021-04-12 11:28 ` Cyril Hrubis
2021-05-17 7:41 ` Pankaj Vinodrao Joshi
2021-05-18 7:23 ` Pankaj Vinodrao Joshi
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=YG7Mbc/ZTnD85SAh@yuki \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox