From: Yash Shinde <Yash.Shinde@windriver.com>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>,
libc-help@sourceware.org
Cc: harish.sadineni@windriver.com
Subject: Re: How to skip/disable individual test cases in glibc testsuite
Date: Wed, 27 Mar 2024 21:05:31 +0530 [thread overview]
Message-ID: <4b5576a0-a1c6-4d14-9a46-49c3e8acdd4e@windriver.com> (raw)
In-Reply-To: <8cf9bc35-b2ad-4eec-8a34-25bf3c7d54d4@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 954 bytes --]
On 27-03-2024 19:36, Adhemerval Zanella Netto wrote:
> There is no straightforwards way to exclude the tests without changing
> the sysdeps/unix/sysv/linux/Makefile. Do you know why qemu-user is
> stuck? All tests should have a watchdog one to trigger a kill for
> the timeout case, it would be useful to know why this is not working
> on this particular environment.
>
> PS: for some reason your email went to my spam box, not sure why.
Thanks for looking into it.
What changes should be done in "sysdeps/unix/sysv/linux/Makefile " to
skip a test case?
I checked for why qemu-user is stucked and it was found that the test
case "sysdeps/unix/sysv/linux/tst-scm_rights-time64.c" has some
"recvmsg/sendmsg" subprocess to the parent process.
I guess this processes do not terminate correctly and thus there are
stale qemu processes.
How do I check if the watchdog works correctly and triggers a kill for
timeout case(int this particular case)?
next prev parent reply other threads:[~2024-03-27 15:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 13:55 Yash Shinde
2024-03-19 6:47 ` Yash Shinde
2024-03-27 14:06 ` Adhemerval Zanella Netto
2024-03-27 15:35 ` Yash Shinde [this message]
2024-03-28 13:13 ` Adhemerval Zanella Netto
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=4b5576a0-a1c6-4d14-9a46-49c3e8acdd4e@windriver.com \
--to=yash.shinde@windriver.com \
--cc=adhemerval.zanella@linaro.org \
--cc=harish.sadineni@windriver.com \
--cc=libc-help@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).