Skip to content

Use standard runners for issue triage framework jobs - #55661

Draft
nagilson wants to merge 1 commit into
dotnet:mainfrom
nagilson:nagilson-fix-issue-triage-runner-timeout
Draft

Use standard runners for issue triage framework jobs#55661
nagilson wants to merge 1 commit into
dotnet:mainfrom
nagilson:nagilson-fix-issue-triage-runner-timeout

Conversation

@nagilson

@nagilson nagilson commented Aug 7, 2026

Copy link
Copy Markdown
Member

Summary

  • keep roles: all; non-maintainer issue authors are already authorized
  • run gh-aw framework jobs on ubuntu-latest instead of ubuntu-slim
  • avoid the single-CPU runner's hard 15-minute job timeout canceling triage before any step executes

Root cause

The workflow did trigger for non-maintainer issue #55639 as actor damienhoneyford, but its pre_activation job never acquired a runner and was canceled after exactly 15 minutes with runner_id: 0, zero steps, and zero billable milliseconds:

https://github.com/dotnet/sdk/actions/runs/31119268940

GitHub documents that ubuntu-slim has 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: all allows any user and runs-on-slim controls 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 by Toxitricity with author_association: NONE, automatically triggered and completed successfully:

https://github.com/nagilson/sdk/actions/runs/31130404269

Validation

gh aw compile issue-triage --strict completed 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-latest label and completed that job successfully.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@azure-pipelines

Copy link
Copy Markdown
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.

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.

Agentic Triager does not Triage non maintainer issues

1 participant