All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michal Sieron" <michalwsieron@gmail.com>
To: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH v2 00/10] hashserv: Pipeline Upstream Queries
Date: Fri, 31 Jul 2026 06:05:45 -0700	[thread overview]
Message-ID: <1147544.1785503145144982751@lists.openembedded.org> (raw)
In-Reply-To: <20260730183254.793698-1-JPEWhacker@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 5383 bytes --]

Hi,

something is not working for me...

In the first run I got it stuck for an hour at:
WARNING: Error contacting Hash Equivalence Server unix:///path/to/my/workdir/builds/yoctobuild/hashserve.sock: Sent 192 messages but only received 49
WARNING: Error contacting Hash Equivalence Server unix:///path/to/my/workdir/builds/yoctobuild/hashserve.sock: Sent 115 messages but only received 0
WARNING: Error contacting Hash Equivalence Server unix:///path/to/my/workdir/builds/yoctobuild/hashserve.sock: Sent 115 messages but only received 0
WARNING: Error contacting Hash Equivalence Server unix:///path/to/my/workdir/builds/yoctobuild/hashserve.sock: Sent 165 messages but only received 0
WARNING: Error contacting Hash Equivalence Server unix:///path/to/my/workdir/builds/yoctobuild/hashserve.sock: Sent 9 messages but only received 4
WARNING: Error contacting Hash Equivalence Server unix:///path/to/my/workdir/builds/yoctobuild/hashserve.sock: Sent 99 messages but only received 0
WARNING: Error contacting Hash Equivalence Server unix:///path/to/my/workdir/builds/yoctobuild/hashserve.sock: Sent 15 messages but only received 0
WARNING: Error contacting Hash Equivalence Server unix:///path/to/my/workdir/builds/yoctobuild/hashserve.sock: Sent 9 messages but only received 0
WARNING: Error contacting Hash Equivalence Server unix:///path/to/my/workdir/builds/yoctobuild/hashserve.sock: Sent 1 messages but only received 0
WARNING: Error contacting Hash Equivalence Server unix:///path/to/my/workdir/builds/yoctobuild/hashserve.sock: Sent 4 messages but only received 0
WARNING: Error contacting Hash Equivalence Server unix:///path/to/my/workdir/builds/yoctobuild/hashserve.sock: Sent 47 messages but only received 0
WARNING: Error contacting Hash Equivalence Server unix:///path/to/my/workdir/builds/yoctobuild/hashserve.sock: Sent 1 messages but only received 0
WARNING: Error contacting Hash Equivalence Server unix:///path/to/my/workdir/builds/yoctobuild/hashserve.sock: Sent 116 messages but only received 0
WARNING: Error contacting Hash Equivalence Server unix:///path/to/my/workdir/builds/yoctobuild/hashserve.sock: Sent 112 messages but only received 0
WARNING: Error contacting Hash Equivalence Server unix:///path/to/my/workdir/builds/yoctobuild/hashserve.sock: Sent 117 messages but only received 0
WARNING: Error contacting Hash Equivalence Server unix:///path/to/my/workdir/builds/yoctobuild/hashserve.sock: Sent 277 messages but only received 0
WARNING: Error contacting Hash Equivalence Server unix:///path/to/my/workdir/builds/yoctobuild/hashserve.sock: Sent 66 messages but only received 0
WARNING: Error contacting Hash Equivalence Server unix:///path/to/my/workdir/builds/yoctobuild/hashserve.sock: Sent 72 messages but only received 0
WARNING: Error contacting Hash Equivalence Server unix:///path/to/my/workdir/builds/yoctobuild/hashserve.sock: Sent 157 messages but only received 0
WARNING: Error contacting Hash Equivalence Server unix:///path/to/my/workdir/builds/yoctobuild/hashserve.sock: Sent 45 messages but only received 0
WARNING: Error contacting Hash Equivalence Server unix:///path/to/my/workdir/builds/yoctobuild/hashserve.sock: Sent 52 messages but only received 0
WARNING: Error contacting Hash Equivalence Server unix:///path/to/my/workdir/builds/yoctobuild/hashserve.sock: Sent 75 messages but only received 0
WARNING: Error contacting Hash Equivalence Server unix:///path/to/my/workdir/builds/yoctobuild/hashserve.sock: Sent 18 messages but only received 0
WARNING: Error contacting Hash Equivalence Server unix:///path/to/my/workdir/builds/yoctobuild/hashserve.sock: Sent 10 messages but only received 0
WARNING: Error contacting Hash Equivalence Server unix:///path/to/my/workdir/builds/yoctobuild/hashserve.sock: Sent 98 messages but only received 0
Initialising tasks:  44% |##########################################################                                                                           | ETA:  1:03:30

Then in another run, after reporting that 8 messages were sent, but 0 received, hashserve.sock disappeared!
WARNING: Error contacting Hash Equivalence Server unix:///path/to/my/workdir/builds/yoctobuild/hashserve.sock: Sent 8 messages but only received 0
WARNING: Error contacting Hash Equivalence Server unix:///path/to/my/workdir/builds/yoctobuild/hashserve.sock: [Errno 2] No such file or directory
WARNING: Error contacting Hash Equivalence Server unix:///path/to/my/workdir/builds/yoctobuild/hashserve.sock: [Errno 2] No such file or directory
WARNING: Error contacting Hash Equivalence Server unix:///path/to/my/workdir/builds/yoctobuild/hashserve.sock: [Errno 2] No such file or directory
Although that might be a different issue after killing previous run and not making sure all Cooker processes are actually dead?

Anyway, after properly making sure there are no lingering processes, I am still getting stuck at:
WARNING: [...] Sent 192 messages but only received 26
WARNING: [...] Sent 115 messages but only received 0
WARNING: [...] Sent 115 messages but only received 0
WARNING: [...] Sent 165 messages but only received 0
WARNING: [...] Sent 9 messages but only received 1

I will be going on vacation now, so unfortunately, I won't be able to test more if you come up with anything new.

Best regards,
Michal

[-- Attachment #2: Type: text/html, Size: 5929 bytes --]

  parent reply	other threads:[~2026-07-31 13:05 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-24 21:25 [bitbake-devel][PATCH 0/6] hashserv: Pipeline Upstream Queries Joshua Watt
2026-07-24 21:25 ` [bitbake-devel][PATCH 1/6] hashserv: client: Add asynchronous streaming API Joshua Watt
2026-07-24 21:25 ` [bitbake-devel][PATCH 2/6] hashserv: server: Fix formatting Joshua Watt
2026-07-24 21:25 ` [bitbake-devel][PATCH 3/6] hashserv: server: Add queued streaming API Joshua Watt
2026-07-24 21:25 ` [bitbake-devel][PATCH 4/6] hashserv: server: Use streaming and queue API for upstream unihash queries Joshua Watt
2026-07-24 21:25 ` [bitbake-devel][PATCH 5/6] hashserv: server: Use streaming and queue API for upstream exist queries Joshua Watt
2026-07-24 21:25 ` [bitbake-devel][PATCH 6/6] hashserv: tests: Add test for upstream pipelining Joshua Watt
2026-07-26 13:50 ` [bitbake-devel][PATCH 0/6] hashserv: Pipeline Upstream Queries Richard Purdie
2026-07-30 18:30 ` [bitbake-devel][PATCH v2 00/10] " Joshua Watt
2026-07-30 18:30   ` [bitbake-devel][PATCH v2 01/10] asyncrpc: Add Task Group Joshua Watt
2026-07-30 18:30   ` [bitbake-devel][PATCH v2 02/10] asyncrpc: serv: Use " Joshua Watt
2026-07-30 18:30   ` [bitbake-devel][PATCH v2 03/10] asyncrpc: serv: Cancel all clients on server stop Joshua Watt
2026-07-30 18:30   ` [bitbake-devel][PATCH v2 04/10] hashserv: tests: Improve test logging Joshua Watt
2026-07-30 18:30   ` [bitbake-devel][PATCH v2 05/10] hashserv: client: Add asynchronous streaming API Joshua Watt
2026-07-30 18:30   ` [bitbake-devel][PATCH v2 06/10] hashserv: server: Add queued " Joshua Watt
2026-07-30 18:31   ` [bitbake-devel][PATCH v2 07/10] hashserv: server: Use streaming and queue API for upstream unihash queries Joshua Watt
2026-07-30 18:31   ` [bitbake-devel][PATCH v2 08/10] hashserv: server: Use streaming and queue API for upstream exist queries Joshua Watt
2026-07-30 18:31   ` [bitbake-devel][PATCH v2 09/10] hashserv: tests: Add more upstream tests Joshua Watt
2026-07-30 18:31   ` [bitbake-devel][PATCH v2 10/10] hashserv: tests: Add test for upstream pipelining Joshua Watt
2026-07-31 13:05   ` Michal Sieron [this message]
2026-08-26 20:05     ` [bitbake-devel] [PATCH v2 00/10] hashserv: Pipeline Upstream Queries Joshua Watt
2026-08-26 22:48       ` Michal Sieron
2026-08-27 18:57         ` [bitbake-devel] " Joshua Watt
2026-08-28 15:58   ` [bitbake-devel][PATCH v3 00/11] " Joshua Watt
2026-08-28 15:58     ` [bitbake-devel][PATCH v3 01/11] asyncrpc: Add Task Group Joshua Watt
2026-08-28 15:58     ` [bitbake-devel][PATCH v3 02/11] asyncrpc: serv: Use " Joshua Watt
2026-08-28 15:58     ` [bitbake-devel][PATCH v3 03/11] asyncrpc: serv: Cancel all clients on server stop Joshua Watt
2026-08-28 15:58     ` [bitbake-devel][PATCH v3 04/11] hashserv: tests: Improve test logging Joshua Watt
2026-08-28 15:58     ` [bitbake-devel][PATCH v3 05/11] hashserv: client: Add asynchronous streaming API Joshua Watt
2026-08-28 15:58     ` [bitbake-devel][PATCH v3 06/11] hashserv: server: Add queued " Joshua Watt
2026-08-28 15:58     ` [bitbake-devel][PATCH v3 07/11] hashserv: server: Use streaming and queue API for upstream unihash queries Joshua Watt
2026-08-28 15:58     ` [bitbake-devel][PATCH v3 08/11] hashserv: server: Use streaming and queue API for upstream exist queries Joshua Watt
2026-08-28 15:58     ` [bitbake-devel][PATCH v3 09/11] hashserv: tests: Add more upstream tests Joshua Watt
2026-08-28 15:58     ` [bitbake-devel][PATCH v3 10/11] hashserv: tests: Add test for upstream pipelining Joshua Watt
2026-08-28 15:58     ` [bitbake-devel][PATCH v3 11/11] hashserv: server: Fix upstream get-unihash miss truncating stream Joshua Watt

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=1147544.1785503145144982751@lists.openembedded.org \
    --to=michalwsieron@gmail.com \
    --cc=bitbake-devel@lists.openembedded.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 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.