Skip to content

Use standard runners for issue triage framework jobs - #55661

Open
nagilson wants to merge 3 commits into
dotnet:mainfrom
nagilson:nagilson-fix-issue-triage-runner-timeout
Open

Use standard runners for issue triage framework jobs#55661
nagilson wants to merge 3 commits 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.

@nagilson
nagilson requested a review from a team August 7, 2026 19:05
@nagilson
nagilson marked this pull request as ready for review August 7, 2026 19:06
Copilot AI review requested due to automatic review settings August 7, 2026 19:06
@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.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

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-latest to the issue-triage workflow frontmatter to override the runner label used for generated framework jobs.
  • Regenerate the compiled workflow (issue-triage.lock.yml) so affected jobs now use runs-on: ubuntu-latest instead of ubuntu-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).

Comment thread .github/workflows/issue-triage.md
@nagilson
nagilson marked this pull request as draft August 7, 2026 19:32
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: afe1f3cd-6b67-4beb-96a6-5126feb36f28
@nagilson
nagilson requested a review from Copilot August 7, 2026 19:48
@nagilson

nagilson commented Aug 7, 2026

Copy link
Copy Markdown
Member Author

new changes seem successful: https://github.com/nagilson/sdk/actions/runs/31212492533

@nagilson
nagilson marked this pull request as ready for review August 7, 2026 19:49
@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.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

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-slim 15-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.

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

2 participants