Use standard runners for issue triage framework jobs - #55661
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Azure Pipelines: Successfully started running 2 pipeline(s). 1 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
|
Azure Pipelines: Successfully started running 2 pipeline(s). 1 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
There was a problem hiding this comment.
Pull request overview
This PR adjusts the issue-triage agentic workflow configuration to avoid the hard 15-minute timeout associated with ubuntu-slim runners by switching generated framework jobs to run on standard GitHub-hosted runners (ubuntu-latest). This is intended to prevent triage from being cancelled due to runner allocation delays, especially for non-maintainer issue authors.
Changes:
- Add
runs-on-slim: ubuntu-latestto theissue-triageworkflow frontmatter to override the runner label used for generated framework jobs. - Regenerate the compiled workflow (
issue-triage.lock.yml) so affected jobs now useruns-on: ubuntu-latestinstead ofubuntu-slim.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| .github/workflows/issue-triage.md | Adds frontmatter to run generated framework jobs on ubuntu-latest to avoid ubuntu-slim hard timeouts. |
| .github/workflows/issue-triage.lock.yml | Updates the generated workflow so framework jobs run on ubuntu-latest (reflecting the new frontmatter). |
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: afe1f3cd-6b67-4beb-96a6-5126feb36f28
|
new changes seem successful: https://github.com/nagilson/sdk/actions/runs/31212492533 |
|
Azure Pipelines: Successfully started running 2 pipeline(s). 1 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 6 out of 6 changed files in this pull request and generated no new comments.
Suppressed comments (1)
.github/workflows/shared/pat_pool.README.md:79
- The README claims the
ubuntu-slim15-minute limit includes time spent waiting for runner allocation. GitHub’s normal job timeouts don’t count queued time, so this wording is likely inaccurate; better to describe the observed behavior (jobs can be canceled before steps start if allocation is delayed) without asserting how the limit is computed.
The shared `pat_pool` job runs on `ubuntu-latest`. Do not change it to `ubuntu-slim`, which has a hard 15-minute job limit that includes time spent waiting for runner allocation.
Summary
roles: all; non-maintainer issue authors are already authorizedubuntu-latestinstead ofubuntu-slimRoot cause
The workflow did trigger for non-maintainer issue #55639 as actor
damienhoneyford, but itspre_activationjob never acquired a runner and was canceled after exactly 15 minutes withrunner_id: 0, zero steps, and zero billable milliseconds:https://github.com/dotnet/sdk/actions/runs/31119268940
GitHub documents that
ubuntu-slimhas a hard 15-minute job timeout:https://docs.github.com/en/actions/reference/runners/github-hosted-runners#single-cpu-runners
The gh-aw documentation says
roles: allallows any user andruns-on-slimcontrols generated framework jobs:https://github.github.com/gh-aw/reference/triggers/
https://github.github.com/gh-aw/reference/frontmatter/
A separate fork test confirms the existing permissions work for a non-maintainer. Issue
nagilson/sdk#128, opened byToxitricitywithauthor_association: NONE, automatically triggered and completed successfully:https://github.com/nagilson/sdk/actions/runs/31130404269
Validation
gh aw compile issue-triage --strictcompleted with zero errors and zero warnings.Fixes #55652
Live branch-ref validation: https://github.com/nagilson/sdk/actions/runs/31133889908 assigned pre_activation to the requested
ubuntu-latestlabel and completed that job successfully.