From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Joshua Watt <JPEWhacker@gmail.com>,
Michael Halstead <mhalstead@linuxfoundation.org>,
bitbake-devel <bitbake-devel@lists.openembedded.org>
Subject: Re: [bitbake-devel] One remaining hashserv issue - bitbake-selftest failure on some hosts
Date: Sun, 14 Apr 2024 22:08:54 +0100 [thread overview]
Message-ID: <0a26e1afe4f043570c7b94b0a818e4ce77a43d26.camel@linuxfoundation.org> (raw)
In-Reply-To: <17C611708D6AA374.8361@lists.openembedded.org>
On Sun, 2024-04-14 at 07:24 +0100, Richard Purdie via
lists.openembedded.org wrote:
> We've managed to get most issues resolved, thanks!
>
> I think the one remaining puzzling issue left are these:
>
> debian11-ty-3:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/6583/steps/11/logs/stdio
> debian11-ty-1:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/6586/steps/11/logs/stdio
> ubunbtu2004-arm-1:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/127/builds/3182/steps/11/logs/stdio
>
> I think these have only appeared since we changed the websockets
> presence on the workers and it appears host specific.
>
> We've seen this issue with master (which Joshua's changes unmerged) and
> on master-next with Joshua's patches.
>
> Ideas welcome...
>
Its worth noting we started seeing these on specific workers when
master hadn't changed and we hadn't enabled the new hash server. This
means it is likely the installation of websockets on the workers
triggered the issues.
Cheers,
Richard
next parent reply other threads:[~2024-04-14 21:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <17C611708D6AA374.8361@lists.openembedded.org>
2024-04-14 21:08 ` Richard Purdie [this message]
2024-04-15 17:16 ` [bitbake-devel] One remaining hashserv issue - bitbake-selftest failure on some hosts Michael Halstead
2024-04-16 6:49 ` Richard Purdie
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=0a26e1afe4f043570c7b94b0a818e4ce77a43d26.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=JPEWhacker@gmail.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=mhalstead@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).