Skip to content

Agent timeout (20min) blocks large projects: nushell, Dapper, Polly #948

@Mossaka

Description

@Mossaka

Summary

In the AWF Build/Test Experiment v3, three repos hit the 20-minute agent timeout before completing their build/test cycle:

Repo Language What Happened
nushell Rust Large Rust workspace — compilation alone may exceed 20 minutes
Dapper .NET Build succeeded but dotnet test exceeded the timeout
Polly .NET Build succeeded but dotnet test exceeded the timeout

Impact

  • 3 repos out of 98 (3%) are affected
  • For Dapper and Polly, the builds actually succeed — only the test phase times out
  • nushell is a very large Rust workspace (100+ crates) that needs more compile time

Suggestion

Consider one or more of:

  1. Increase default timeout to 30 or 45 minutes for build-test workflows
  2. Allow per-workflow timeout configuration in the frontmatter (e.g., timeout: 45)
  3. Split build and test phases so a timeout during testing still reports the build result

Experiment Context

  • gh-aw: v0.45.2, AWF: v0.19.1
  • Full report: AWF Build/Test Experiment v3 (Feb 17, 2026)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions