Skip to content

ci: use BB_HASHSERVE=auto fallback for fork PRs - #16627

Merged
rpcme merged 1 commit into
master-nextfrom
fix/hashserv-auto-fallback
Aug 10, 2026
Merged

rpcme merged 1 commit into
master-nextfrom
fix/hashserv-auto-fallback

Conversation

@rpcme

@rpcme rpcme commented Aug 10, 2026

Copy link
Copy Markdown
Member

Problem

OE-core master now enables OEEquivHash at the distro level (not just local.conf). Previous fix attempts:

  • Setting BB_SIGNATURE_HANDLER = "OEBasicHash" → doesn't override distro-level config
  • Not setting BB_HASHSERVE → bitbake defaults to local sqlite DB at SSTATE_DIR which fails on NFS

Result:

ERROR: Hash equivalency database location (set via BB_HASHSERVE_DB_DIR to /sstate-cache)
cannot be on a NFS mount due to potential NFS locking issues

Fix

Use BB_HASHSERVE = "auto" as the fallback. This tells bitbake to start a local in-memory hash equivalency server within the process itself — no NFS DB, no network dependency, no external server needed.

Context BB_HASHSERVE Effect
Internal PRs hashserv-<release>.internal:8686 Remote shared server, full sstate sharing
Fork PRs auto Local in-memory server, no sharing but functional

Both always use BB_SIGNATURE_HANDLER = "OEEquivHash" since the distro mandates it.

Unblocks #16292.

OE-core master now enables OEEquivHash by default in the distro
config. Setting BB_SIGNATURE_HANDLER=OEBasicHash in local.conf
cannot override this (distro config takes precedence). Without a
valid BB_HASHSERVE, bitbake tries to use a local sqlite DB at
SSTATE_DIR which fails on the NFS-mounted /sstate-cache:

  ERROR: Hash equivalency database location (BB_HASHSERVE_DB_DIR)
  cannot be on a NFS mount

Fix: use BB_HASHSERVE="auto" as fallback for fork PRs. This starts
a local in-memory hash equivalency server within bitbake, satisfying
the OEEquivHash requirement without needing network access or a
writable non-NFS filesystem.

- Internal PRs: BB_HASHSERVE=<remote server> (shared sstate)
- Fork PRs: BB_HASHSERVE=auto (local, no sharing but functional)
@rpcme
rpcme requested a review from a team as a code owner August 10, 2026 12:27
@rpcme
rpcme merged commit 4733b03 into master-next Aug 10, 2026
7 of 11 checks passed
@rpcme
rpcme deleted the fix/hashserv-auto-fallback branch August 10, 2026 12:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant