Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Pratik Farkase" <pratik.farkase@est.tech>,
	<openembedded-core@lists.openembedded.org>
Cc: <pratik.farkase@ericsson.com>
Subject: Re: [OE-core][PATCH v1] psmisc: add ptest support
Date: Tue, 15 Sep 2026 15:22:53 +0200	[thread overview]
Message-ID: <DLFX7NYAA4GM.WL30OCNY86BL@bootlin.com> (raw)
In-Reply-To: <20260914130447.107189-1-pratik.farkase@est.tech>

Hi,

On Mon Sep 14, 2026 at 3:04 PM CEST, Pratik Farkase wrote:
> Add ptest support using psmisc's upstream DejaGnu testsuite, which
> exercises killall, pslog and fuser via their .exp scripts. The tools and
> the testsuite helper programs (socket_test, test-listen) are installed
> under a src/ layout so the scripts' ${topdir}src/<tool> paths resolve on
> target.

I'm seeing failures for these ptest on our test infrastructure:

AssertionError: 
Failed ptests:
{'psmisc': ['fuser_-a_no_proc', 'fuser_-av,_no_proc', 'fuser_-va,_no_proc']}

Full log: https://autobuilder.yoctoproject.org/valkyrie/api/v2/logs/8929945/raw_inline

Similar failures:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/61/builds/4533
https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/4560

Can you have a look at these?

Thanks,
Antonin


  reply	other threads:[~2026-09-15 13:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-14 13:04 [OE-core][PATCH v1] psmisc: add ptest support Pratik Farkase
2026-09-15 13:22 ` Antonin Godard [this message]
2026-09-16  8:16 ` [OE-core][PATCH v2] " Pratik Farkase
2026-09-16  8:31   ` Patchtest results for " patchtest
2026-09-16  9:15 ` Pratik Farkase
2026-09-21  7:36   ` Antonin Godard
2026-09-18  9:36 ` Pratik Farkase
2026-09-21 12:31 ` [OE-core][PATCH v3] " Pratik Farkase
2026-09-21 12:46   ` Patchtest results for " patchtest
2026-09-21 12:57 ` Pratik Farkase

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=DLFX7NYAA4GM.WL30OCNY86BL@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=pratik.farkase@ericsson.com \
    --cc=pratik.farkase@est.tech \
    /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