Skip to content

fix: run browser artifact detect job on ubuntu-latest-large - #3937

Open
harsh-joshi99 wants to merge 1 commit into
build-browser-destinations-workflowfrom
fix/browser-detect-runner-label
Open

fix: run browser artifact detect job on ubuntu-latest-large#3937
harsh-joshi99 wants to merge 1 commit into
build-browser-destinations-workflowfrom
fix/browser-detect-runner-label

Conversation

@harsh-joshi99

Copy link
Copy Markdown
Contributor

Problem

The detect-browser-destination-changes job in publish-browser-destinations.yml requests runs-on: ubuntu-latest, a runner label this org does not serve. As a result the job hangs in the queue indefinitely and the browser artifact is never built.

Verified on staging: a Publish commit's run sat ~1h13m with the detect job unassigned ("Waiting for a runner to pick up this job") while ubuntu-latest-large jobs (CI, etc.) completed normally. After switching the label to ubuntu-latest-large, the detect job was picked up immediately and the build produced the artifact.

Fix

Change the detect job to ubuntu-latest-large, matching this workflow's own build-browser-destinations job (line 75) and every other job in the repo. This targets the #3787 branch so the fix lands with the workflow when it merges to main.

Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com

The detect-browser-destination-changes job requests 'ubuntu-latest', a runner
label this org does not serve, so the job hangs in the queue indefinitely and the
browser artifact is never built (verified on staging: the job sat ~1h13m unassigned
while ubuntu-latest-large jobs completed). Every other job in the repo, including
this workflow's own build job, uses ubuntu-latest-large. Align the detect job.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants