Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <corentin.guillevic@smile.fr>, <bitbake-devel@lists.openembedded.org>
Subject: Re: [bitbake-devel] [PATCH] cooker: limit the execution of the hashequiv client/server ping
Date: Mon, 27 Apr 2026 10:51:20 +0200	[thread overview]
Message-ID: <DI3T4XKSTUPE.Y4MSPXKSLM3S@bootlin.com> (raw)
In-Reply-To: <20260423102950.697501-2-corentin.guillevic@smile.fr>

On Thu Apr 23, 2026 at 12:29 PM CEST, Corentin Guillevic via lists.openembedded.org wrote:
> From: Corentin Guillevic <corentin.guillevic@smile.fr>
>
> The ping method is used to test the connection to the hash equivalence server.
> However, if the server is unavailable, the bitbake server has to wait several
> minutes for the system to terminate.
>
> While waiting for a response from the hash server, the bitbake server does not
> provide any feedback to the bitbake client. The latter then closes the link and
> fails with the error:
>
> Timeout while waiting for a reply from the bitbake server (60s at 09:50:15.377337)
>
> Adding a timeout to the ping step allows quicker action when a remote server is
> unavailable, and prevents disconnection of the client due to timeout.
> The default timeout is 10 seconds, but this can be set using the
> BB_HASHSERVER_TIMEOUT variable.
>
> Signed-off-by: Corentin Guillevic <corentin.guillevic@smile.fr>
> ---

Hi Corentin,

Thanks for your patch.

It looks like this is triggering some oe-selftest failures:

2026-04-24 13:28:03,744 - oe-selftest - INFO - prservice.BitbakePrTests.test_import_export_override_db (subunit.RemotedTestCase)
2026-04-24 13:28:03,746 - oe-selftest - INFO -  ... FAIL
...
  File "/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/layers/openembedded-core/meta/lib/oeqa/selftest/cases/prservice.py", line 115, in test_import_export_override_db
    self.run_test_pr_export_import('m4', replace_current_db=False)
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/layers/openembedded-core/meta/lib/oeqa/selftest/cases/prservice.py", line 89, in run_test_pr_export_import
    self.increment_package_pr(package_name)
    ~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^
  File "/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/layers/openembedded-core/meta/lib/oeqa/selftest/cases/prservice.py", line 61, in increment_package_pr
    self.assertEqual(res.status, 0, msg=res.output)
    ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.13/unittest/case.py", line 907, in assertEqual
    assertion_func(first, second, msg=msg)
    ~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.13/unittest/case.py", line 900, in _baseAssertEqual
    raise self.failureException(msg)
AssertionError: 1 != 0 : NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)... (13:28:02.531366)
NOTE: Started PRServer with DBfile: /srv/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-1371670/cache/prserv.sqlite3, Address: 127.0.0.1:37647, PID: 2273277
ERROR: PRservice localhost:37647 not available
ERROR: Unable to start PR Server, exiting, check the bitbake-cookerdaemon.log
...
2026-04-24 13:28:06,081 - oe-selftest - INFO - prservice.BitbakePrTests.test_import_export_replace_db (subunit.RemotedTestCase)
2026-04-24 13:28:06,081 - oe-selftest - INFO -  ... FAIL
...
2026-04-24 13:28:08,453 - oe-selftest - INFO - prservice.BitbakePrTests.test_pr_service_deb_arch_dep (subunit.RemotedTestCase)
2026-04-24 13:28:08,453 - oe-selftest - INFO -  ... FAIL
...
2026-04-24 13:28:10,791 - oe-selftest - INFO - prservice.BitbakePrTests.test_pr_service_deb_arch_indep (subunit.RemotedTestCase)
2026-04-24 13:28:10,792 - oe-selftest - INFO -  ... FAIL
...
2026-04-24 13:28:13,383 - oe-selftest - INFO - prservice.BitbakePrTests.test_pr_service_ipk_arch_dep (subunit.RemotedTestCase)
2026-04-24 13:28:13,384 - oe-selftest - INFO -  ... FAIL
...
2026-04-24 13:28:15,719 - oe-selftest - INFO - prservice.BitbakePrTests.test_pr_service_ipk_arch_indep (subunit.RemotedTestCase)
2026-04-24 13:28:15,720 - oe-selftest - INFO -  ... FAIL
...
2026-04-24 13:28:18,037 - oe-selftest - INFO - prservice.BitbakePrTests.test_pr_service_rpm_arch_dep (subunit.RemotedTestCase)
2026-04-24 13:28:18,038 - oe-selftest - INFO -  ... FAIL
...
2026-04-24 13:28:20,344 - oe-selftest - INFO - prservice.BitbakePrTests.test_pr_service_rpm_arch_indep (subunit.RemotedTestCase)
2026-04-24 13:28:20,345 - oe-selftest - INFO -  ... FAIL

https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/3834
https://autobuilder.yoctoproject.org/valkyrie/#/builders/35/builds/3744
https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/3624

Can you have a look at the issue?

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



      parent reply	other threads:[~2026-04-27  8:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-23 10:29 [PATCH] cooker: limit the execution of the hashequiv client/server ping corentin.guillevic
2026-04-23 11:50 ` [bitbake-devel] " Antonin Godard
2026-04-27  8:51 ` Mathieu Dubois-Briand [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=DI3T4XKSTUPE.Y4MSPXKSLM3S@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=corentin.guillevic@smile.fr \
    /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