Skip to content

fix(ci): verify NVIDIA manifest assembly runs on testing branch via API - #545

Open
HuntedRaven7 wants to merge 1 commit into
projectbluefin:mainfrom
HuntedRaven7:issue-544
Open

fix(ci): verify NVIDIA manifest assembly runs on testing branch via API#545
HuntedRaven7 wants to merge 1 commit into
projectbluefin:mainfrom
HuntedRaven7:issue-544

Conversation

@HuntedRaven7

Copy link
Copy Markdown
Collaborator

github.event.workflow_run.head_branch does not reliably report the triggering workflow's branch (always resolves to "main"), so the head_branch == 'testing' condition in build-nvidia-manifest.yml never passed. The manifest assembly never ran, leaving the :testing tag stuck on a stale single-arch manifest which execute-release.yml rejected.

Move the branch check into the find-runs step where each discovered run is verified via the API to have run on the testing branch.

related to #544

github.event.workflow_run.head_branch does not reliably report the
triggering workflow's branch (always resolves to "main"), so the
head_branch == 'testing' condition in build-nvidia-manifest.yml never
passed. The manifest assembly never ran, leaving the :testing tag stuck
on a stale single-arch manifest which execute-release.yml rejected.

Move the branch check into the find-runs step where each discovered
run is verified via the API to have run on the testing branch.

related to projectbluefin#544
@HuntedRaven7
HuntedRaven7 requested a review from a team as a code owner August 26, 2026 13:16

@hanthor hanthor left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Correct fix, and correctly diagnosed: github.event.workflow_run.head_branch is a known-unreliable field for workflow_run-triggered workflows in some configurations, so gating the whole job on it in the top-level if: silently broke manifest assembly for every testing-branch build. Moving the branch check into find_testing_run — resolving each candidate run by ID via /actions/runs/{run_id} and reading its authoritative head_branch — is the right fix, and it fails safe: a non-testing run is treated as "not found" (with a ::warning::) rather than accepted, so ready still correctly gates on both architectures actually having a testing build. Lint & syntax green.


Generated by Claude Code

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.

2 participants