Skip to content

ci: fix BB_HASHSERVE variable lookup case mismatch - #16623

Merged
rpcme merged 1 commit into
master-nextfrom
fix/hashserv-variable-case
Aug 9, 2026
Merged

rpcme merged 1 commit into
master-nextfrom
fix/hashserv-variable-case

Conversation

@rpcme

@rpcme rpcme commented Aug 9, 2026

Copy link
Copy Markdown
Member

Problem

The build-test-recipe workflow fails on all machines with:

ERROR: OEEquivHash requires BB_HASHSERVE to be set

The workflow derives a release name from the branch (e.g., master-next → master) and uses it to look up repository variables via bracket notation:

${{ vars[format('HASHSERV_{0}', needs.changed.outputs.release)] }}

This produces vars['HASHSERV_master'], but GitHub stores variable names uppercased (HASHSERV_MASTER). Bracket notation access is case-sensitive, so the lookup returns empty string.

Fix

Uppercase the release name (tr '[:lower:]' '[:upper:]') before setting the output, so the format produces HASHSERV_MASTER which matches the stored variable.

Testing

The job name will now display as Build, Test qemuarm64 MASTER instead of Build, Test qemuarm64 master — cosmetic only.

This unblocks all PRs currently failing CI (e.g., #16292).

The workflow derives a release name (e.g., 'master') from the branch
and uses it to dynamically look up repository variables via bracket
notation: vars[format('HASHSERV_{0}', release)].

GitHub stores variable names uppercased (HASHSERV_MASTER) and bracket
notation is case-sensitive, so 'HASHSERV_master' resolves to empty.
This causes bitbake to fail with:
  ERROR: OEEquivHash requires BB_HASHSERVE to be set

Fix: uppercase the release name before outputting it so the lookup
matches the stored variable names.
@rpcme
rpcme requested a review from a team as a code owner August 9, 2026 15:22
@rpcme
rpcme merged commit 286f3a2 into master-next Aug 9, 2026
6 of 10 checks passed
@rpcme
rpcme deleted the fix/hashserv-variable-case branch August 9, 2026 15:23
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