On 1/28/26 19:32, Richard Purdie 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.

On Tue, 2026-01-27 at 16:58 +0800, Changqing Li via lists.openembedded.org 
wrote:
From: Changqing Li <[email protected]>

* support ptest for procps TCLIBC is glibc. The configure.ac only match
   LINUX as "linux-gnu", we can patch it to make test can run on musl lib
system, but the upstream testsuite should only run on gnu libc host,
some test cases only suitable for glibc, eg: Some of the error messages
for free command on musl system is not the same as glibc system, which
will make test failed. In order to avoid some other unexpected failure,
just support ptest for glibc.

* procps's testsuite use DejaGnu test framework.  The testsuite is
   expected to run during build time, this implementation create the same
folder structure as the testsuite expected to make it can work well.

Signed-off-by: Changqing Li <[email protected]>
---
  .../distro/include/ptest-packagelists.inc     |  2 +
  meta/recipes-extended/procps/procps/run-ptest | 24 ++++++++
  meta/recipes-extended/procps/procps_4.0.5.bb  | 57 ++++++++++++++++++-
  3 files changed, 81 insertions(+), 2 deletions(-)
  create mode 100644 meta/recipes-extended/procps/procps/run-ptest
This might trigger a ptest warning:

https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/2990

There are two test cases may run failed randomly.   it run "pmap -X pid pid",  and it expects the same total,

 but it is possible that the memory changes between the two walks of mypid's memory. I opened an issue upstream,

and send a V4 patch,  set these two case as XFAIL.


Regards

//changqing


Cheers,

Richard
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#230121): 
https://lists.openembedded.org/g/openembedded-core/message/230121
Mute This Topic: https://lists.openembedded.org/mt/117485471/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to