public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
* How to skip/disable individual test cases in glibc testsuite
@ 2024-03-14 13:55 Yash Shinde
  2024-03-19  6:47 ` Yash Shinde
  2024-03-27 14:06 ` Adhemerval Zanella Netto
  0 siblings, 2 replies; 5+ messages in thread
From: Yash Shinde @ 2024-03-14 13:55 UTC (permalink / raw)
  To: libc-help; +Cc: harish.sadineni

[-- Attachment #1: Type: text/plain, Size: 772 bytes --]

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.

Regards,
Yash

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: How to skip/disable individual test cases in glibc testsuite
  2024-03-14 13:55 How to skip/disable individual test cases in glibc testsuite Yash Shinde
@ 2024-03-19  6:47 ` Yash Shinde
  2024-03-27 14:06 ` Adhemerval Zanella Netto
  1 sibling, 0 replies; 5+ messages in thread
From: Yash Shinde @ 2024-03-19  6:47 UTC (permalink / raw)
  To: libc-help; +Cc: harish.sadineni

[-- Attachment #1: Type: text/plain, Size: 916 bytes --]

Hi,

Just a gentle reminder.
Any updates to this query?

On 14-03-2024 19:25, 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.
>
> Regards,
> Yash
>

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: How to skip/disable individual test cases in glibc testsuite
  2024-03-14 13:55 How to skip/disable individual test cases in glibc testsuite Yash Shinde
  2024-03-19  6:47 ` Yash Shinde
@ 2024-03-27 14:06 ` Adhemerval Zanella Netto
  2024-03-27 15:35   ` Yash Shinde
  1 sibling, 1 reply; 5+ messages in thread
From: Adhemerval Zanella Netto @ 2024-03-27 14:06 UTC (permalink / raw)
  To: Yash Shinde, libc-help; +Cc: harish.sadineni



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.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: How to skip/disable individual test cases in glibc testsuite
  2024-03-27 14:06 ` Adhemerval Zanella Netto
@ 2024-03-27 15:35   ` Yash Shinde
  2024-03-28 13:13     ` Adhemerval Zanella Netto
  0 siblings, 1 reply; 5+ messages in thread
From: Yash Shinde @ 2024-03-27 15:35 UTC (permalink / raw)
  To: Adhemerval Zanella Netto, libc-help; +Cc: harish.sadineni

[-- 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)?

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: How to skip/disable individual test cases in glibc testsuite
  2024-03-27 15:35   ` Yash Shinde
@ 2024-03-28 13:13     ` Adhemerval Zanella Netto
  0 siblings, 0 replies; 5+ messages in thread
From: Adhemerval Zanella Netto @ 2024-03-28 13:13 UTC (permalink / raw)
  To: Yash Shinde, libc-help; +Cc: harish.sadineni



On 27/03/24 12:35, Yash Shinde wrote:
> 
> 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?

You either remove or comment it out from 'tests' and/or 'tests-time64' rule.

> 
> 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)?
> 

Mostly of testsuite (some old tests does not follow this unfortunately) fork
before actually executing the test, the parent process will be responsible
to watchdog the result and thus killing the process if the default timeout
expires.

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2024-03-28 13:13 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-03-14 13:55 How to skip/disable individual test cases in glibc testsuite Yash Shinde
2024-03-19  6:47 ` Yash Shinde
2024-03-27 14:06 ` Adhemerval Zanella Netto
2024-03-27 15:35   ` Yash Shinde
2024-03-28 13:13     ` Adhemerval Zanella Netto

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).