From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: Yash Shinde <Yash.Shinde@windriver.com>, 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 11:06:19 -0300 [thread overview]
Message-ID: <8cf9bc35-b2ad-4eec-8a34-25bf3c7d54d4@linaro.org> (raw)
In-Reply-To: <43e45a42-62c3-4d4b-9ff7-3a01c099f56f@windriver.com>
On 14/03/24 10:55, Yash Shinde wrote:
> Hi,
>
> After running glibc testsuite with remote host testing using qemu, some stale qemu processes are left behind without terminating as follows:
>
> $ ps -el | grep qemu
> 1 S 23306 2592477 1 0 80 0 - 1101979 sigsus ? 00:00:00 qemu-ppc
> 1 S 23306 2592807 1 0 80 0 - 1101979 sigsus ? 00:00:00 qemu-ppc
>
> The cause of this stale processes are found to be from test cases *tst-scm_rights.c and tst-scm_rights-time64.c files(present at sysdeps/unix/sysv/linux/).
>
> *https://sourceware.org/glibc/wiki/Testing/Testsuite*
> *I referred the above link for checking if the tests can be disabled but didn't find.
>
> Is there any way to skip/disable individual test cases for glibc testsuite?
> If yes, how to do so?
>
> Thanks in advance.
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.
next prev parent reply other threads:[~2024-03-27 14:06 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 [this message]
2024-03-27 15:35 ` Yash Shinde
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=8cf9bc35-b2ad-4eec-8a34-25bf3c7d54d4@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=Yash.Shinde@windriver.com \
--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).