All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: bbnpreetsingh@gmail.com, bitbake-devel@lists.openembedded.org
Cc: Michael Opdenacker <michael.opdenacker@rootcommit.com>
Subject: Re: [bitbake-devel] [PATCH] prserv: add --status to list running servers
Date: Mon, 07 Sep 2026 20:58:26 +0100	[thread overview]
Message-ID: <c842e0a047d06841610d0087df00b76b94cc1114.camel@linuxfoundation.org> (raw)
In-Reply-To: <20260824045011.7-1-bbnpreetsingh@gmail.com>

On Mon, 2026-08-24 at 04:50 +0000, Baban via lists.openembedded.org wrote:
> bitbake-prserv could start and stop a server but not say what is
> running. Add --status: it reads every /tmp/PRServer_<ip>_<port>.pid,
> reports each server as running (with its pid) or as a stale pidfile,
> and exits 0 if at least one server is alive, 1 otherwise.
> 
> Extend the ScriptTests start/stop lifecycle with status checks in
> both states.
> 
> [YOCTO #10865]
> 
> Signed-off-by: Babanpreet Singh <bbnpreetsingh@gmail.com>
> ---
>  bin/bitbake-prserv  |  7 +++++++
>  lib/prserv/serv.py  | 23 +++++++++++++++++++++++
>  lib/prserv/tests.py | 16 +++++++++++++++-
>  3 files changed, 45 insertions(+), 1 deletion(-)

Thanks for this, I've been meaning to do this for a long time!

Unfortunately this patch does seem to be causing failures in our
automated testing:

https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/4607

I did wonder if the code needs to cope with the port already being in
use too?

Cheers,

Richard





      parent reply	other threads:[~2026-09-07 19:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-24  4:50 [PATCH] prserv: add --status to list running servers Babanpreet Singh
2026-08-30 21:55 ` Babanpreet Singh
2026-09-07 19:58 ` Richard Purdie [this message]

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=c842e0a047d06841610d0087df00b76b94cc1114.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bbnpreetsingh@gmail.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=michael.opdenacker@rootcommit.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.