Skip to content

[CI] AcesShared agent hangs until job timeout and ignores cancellation #26569

Description

@dalexsoto

Failure signature

An AcesShared agent becomes unresponsive during an active task:

  • The task produces no finalized Azure DevOps log.
  • The job reaches the 180-minute hard limit.
  • Azure reports that the agent did not respond to cancellation within five minutes.
  • Post-job diagnostics and artifact publication cannot complete reliably.

Stable signature:

AcesShared agent becomes unresponsive during an active task, produces no finalized task log, exceeds the 180-minute job limit, and ignores the 5-minute cancellation request

Confirmed occurrences

PR #26424

  • Head: b4abc54c0c077b0e1515c5b386a94b723f76f8d1
  • Build: 15164848, attempt 1, T: framework / Install dotnet workloads
  • The attempt-1 task log was not finalized and is no longer retained.
  • Azure reported the 180-minute timeout and unresponsive cancellation behavior.
  • Failed-jobs attempt 2 reran T: framework on AcesShared 38 and succeeded from 2026-09-01T10:09:18Z to 10:20:06Z; build 15164848 completed successfully at 10:29:58Z.
  • Worker identity for the failed attempt is unavailable from retained authorized diagnostics.

PR #26568

  • Head: 4237a344488a1ab2c7cee633ec9b95fa8e9f7afb
  • Build: 15218580, attempt 1, Build macOS tests / Build
  • Worker: AcesShared 4
  • Job started at 2026-09-04T20:10:11Z; Build started at 20:17:12Z.
  • The Build task produced no finalized log. Azure failed the stage at 23:15:12Z after the 180-minute cap and reported that the agent ignored cancellation for five minutes.
  • Package macOS tests never ran, so the downstream macOS 27 test stage could not start.
  • Retry is deferred until build 15218580 becomes terminal. Current usage is 0/25 PR lifetime and 0/10 for the current head.

First observed: 2026-09-01T07:00Z (attempt-1 failure window; exact task completion unavailable because the agent stopped reporting).

Latest observed: 2026-09-04T23:15:12Z.

Recurrence: 2 jobs across 2 distinct monitored PRs.

Classification and impact

This is a CI infrastructure/agent failure, not a source regression:

  • It occurred in unrelated tasks (Install dotnet workloads and Build) on unrelated merge PRs.
  • Both tasks stopped reporting without a finalized task log.
  • Azure emitted the same job-limit and cancellation-timeout symptoms.
  • The current PR changes only Xtro baseline files, and the same macOS build job previously completed successfully in about 36 minutes on build 15214043.

The failure blocks downstream stages and can suppress the diagnostic artifacts needed to identify a task-level cause.

Investigation performed

Workaround

Rerun failed jobs after the build is terminal and normal head, mergeability, active-attempt, and retry-budget gates permit it. A durable fix needs agent-side diagnostics or watchdog handling that can survive an unresponsive task process and preserve the last task state.

Azure logs and artifacts are retention-limited.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions