Re: [OE-core] [PATCH] glibc: Fix stale qemu processes left after glibc oe-selftest

2024-04-05 Thread Richard Purdie
On Fri, 2024-04-05 at 11:50 +0530, Yash Shinde wrote: > On 02-04-2024 22:20, Khem Raj wrote: > > > You could make the application of the patch conditional upon being the > > > mips or powerpc architectures. > > > > I think that will be more hassle than disabling it for all architectures. > >   > >

Re: [OE-core] [PATCH] glibc: Fix stale qemu processes left after glibc oe-selftest

2024-04-04 Thread Yash Shinde via lists.openembedded.org
On 02-04-2024 22:20, Khem Raj wrote: You could make the application of the patch conditional upon being the mips or powerpc architectures. I think that will be more hassle than disabling it for all architectures. I see that V2 of this patch is already merged with master branch. (https://git.yo

Re: [OE-core] [PATCH] glibc: Fix stale qemu processes left after glibc oe-selftest

2024-04-02 Thread Khem Raj
On Tue, Apr 2, 2024 at 7:29 AM Richard Purdie wrote: > > On Tue, 2024-04-02 at 12:45 +0530, Shinde, Yash via > lists.openembedded.org wrote: > > On 02-04-2024 01:28, Khem Raj wrote: > > it would be better to disable them just for architectures where it > > > fails since it seems to be a workarou

Re: [OE-core] [PATCH] glibc: Fix stale qemu processes left after glibc oe-selftest

2024-04-02 Thread Richard Purdie
On Tue, 2024-04-02 at 12:45 +0530, Shinde, Yash via lists.openembedded.org wrote: >  On 02-04-2024 01:28, Khem Raj wrote: >  it would be better to disable them just for architectures where it > > fails since it seems to be a workaround, it would be good to keep > > it > > as small as possible > >

Re: [OE-core] [PATCH] glibc: Fix stale qemu processes left after glibc oe-selftest

2024-04-02 Thread Shinde, Yash via lists.openembedded.org
On 02-04-2024 01:28, Khem Raj wrote: it would be better to disable them just for architectures where it fails since it seems to be a workaround, it would be good to keep it as small as possible Initially, we implemented the changes to handle only for architectures where it fails and reviewed i

Re: [OE-core] [PATCH] glibc: Fix stale qemu processes left after glibc oe-selftest

2024-04-01 Thread Khem Raj
it would be better to disable them just for architectures where it fails since it seems to be a workaround, it would be good to keep it as small as possible On Mon, Apr 1, 2024 at 1:10 AM Shinde, Yash via lists.openembedded.org wrote: > > From: Yash Shinde > > qemumips and qemuppc were leaving s

Re: [OE-core] [PATCH] glibc: Fix stale qemu processes left after glibc oe-selftest

2024-04-01 Thread Shinde, Yash via lists.openembedded.org
On 01-04-2024 14:36, Randy MacLeod wrote: The short log is misleading since this isn't really a fix. You have: glibc: Fix stale qemu processes left after glibc oe-selftest Will send a V2 with updated short log. Maybe: glibc: Skip 2 qemu tests that can hang in oe-selftest Skipping is wh

Re: [OE-core] [PATCH] glibc: Fix stale qemu processes left after glibc oe-selftest

2024-04-01 Thread Shinde, Yash via lists.openembedded.org
On 01-04-2024 14:36, Randy MacLeod wrote: ** *CAUTION: This email comes from a non Wind River email account!* Do not click links or open attachments unless you recognize the sender and know the content is safe. The short log is misleading since this isn't really a fix. You have: glibc: Fix s

Re: [OE-core] [PATCH] glibc: Fix stale qemu processes left after glibc oe-selftest

2024-04-01 Thread Randy MacLeod
The short log is misleading since this isn't really a fix. You have: glibc: Fix stale qemu processes left after glibc oe-selftest Maybe: glibc: Skip 2 qemu tests that can hang in oe-selftest Skipping is what we want for now but have you tried wrapping the hanging test in a script that runs:

[OE-core] [PATCH] glibc: Fix stale qemu processes left after glibc oe-selftest

2024-04-01 Thread Shinde, Yash via lists.openembedded.org
From: Yash Shinde qemumips and qemuppc were leaving stale processes behind after running glibc oe-selftest. During analysis, it was found that it was due to "tst-scm_rights" and "tst-scm_rights-time64" tests. Disable them so that there are no stale processes left behind. [YOCTO #15423] https://b