Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: Babanpreet Singh <bbnpreetsingh@gmail.com>
To: bitbake-devel@lists.openembedded.org
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
	Michael Opdenacker <michael.opdenacker@rootcommit.com>,
	Babanpreet Singh <bbnpreetsingh@gmail.com>
Subject: Re: [bitbake-devel] [PATCH] prserv: add --status to list running servers
Date: Tue, 15 Sep 2026 05:53:24 +0000	[thread overview]
Message-ID: <20260915055325.7-1-bbnpreetsingh@gmail.com> (raw)
In-Reply-To: <c842e0a047d06841610d0087df00b76b94cc1114.camel@linuxfoundation.org>

On Mon, 2026-09-07 at 20:58 +0100, Richard Purdie wrote:
> 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?

Thanks, and sorry for the noise. The server dies right after writing
its pidfile there. The old stop test didn't catch that either, since
--stop is happy with a stale pidfile. I can't tell from the logs what
kills it on the workers, but a busy port gives me the same failure
locally. I'll send a v2 that makes --start wait for the server and
fail with its error and puts --status on top of that.

Thanks,
Baban


      reply	other threads:[~2026-09-15  5:53 UTC|newest]

Thread overview: 4+ 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 ` [bitbake-devel] " Richard Purdie
2026-09-15  5:53   ` Babanpreet Singh [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=20260915055325.7-1-bbnpreetsingh@gmail.com \
    --to=bbnpreetsingh@gmail.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=michael.opdenacker@rootcommit.com \
    --cc=richard.purdie@linuxfoundation.org \
    /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