[aw] CI Post-Mortem Analysis failed

[github-actions]

Workflow Failure

Workflow: CI Post-Mortem Analysis
Branch: main
Run: https://github.com/dotnet/macios/actions/runs/26702061058

⚠️ Task Could Not Be Completed: The agent reported that the task could not be performed due to an infrastructure or tool failure.

Reasons:

• Cannot access Azure DevOps: The Azure CLI is installed but not authenticated. The workflow requires access to https://devdiv.visualstudio.com/DevDiv to list PR validation builds, download build timelines, and retrieve test artifacts. The ~/.azure/ directory exists but is not writable (PermissionError), preventing authentication configuration. Without Azure DevOps access, I cannot retrieve the CI build data needed for post-mortem analysis.

  CI Post-Mortem Analysis Failed

Missing Tool Access

The CI post-mortem workflow requires authenticated access to Azure DevOps to perform its 4-phase analysis:

Phase 1: Discovery - List all PR-validation builds from the last 7 days

• Requires: az pipelines build list --org https://devdiv.visualstudio.com --project DevDiv

Phase 2: Extraction - Download build timelines and test artifacts

• Requires: az devops invoke --area build --resource timeline
• Requires: az pipelines runs artifact download for TestSummary and HtmlReport artifacts

Phase 3: Classification - Parse NUnit XML from artifacts to identify flaky tests, infrastructure issues, and shared regressions

Phase 4: Issue Actions - File or update GitHub issues based on findings

Current Environment Status

• ✅ Azure CLI installed: /usr/bin/az
• ✅ Azure DevOps extension available: az devops command exists
• ❌ Authentication configured: NO
• ❌ Permission to configure: NO (PermissionError: /home/runner/.azure/azureProfile.json)

Error Details

When attempting to configure Azure DevOps or list builds:

PermissionError: [Errno 13] Permission denied: '/home/runner/.azure/azureProfile.json'

The ~/.azure/ directory exists but is owned by root with restricted permissions, preventing the workflow from authenticating.

What's Needed

To enable this workflow, the environment needs one of:

1. Pre-configured Azure DevOps authentication (PAT token or managed identity)
2. Writable ~/.azure/ directory for the current user
3. Environment variable AZURE_DEVOPS_EXT_PAT with a valid Personal Access Token
4. Alternative authentication method via environment variables

Alternative Approach

If Azure DevOps access cannot be provided in this environment, the CI post-mortem analysis would need to be run in a different environment (e.g., Azure Pipelines itself with SYSTEM_ACCESSTOKEN) or would require pre-downloaded build data to be provided as input.

This is a structured incompletion signal (report_incomplete), not a real task outcome. Any other safe outputs emitted alongside this signal (e.g., comments) describe the failure state, not a completed review or action.

Action Required

Assign this issue to an agent to debug and fix the issue.

Debug with any coding agent

Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.):

Debug the agentic workflow failure using https://raw.githubusercontent.com/github/gh-aw/main/debug.md

The failed workflow run is at https://github.com/dotnet/macios/actions/runs/26702061058

Manually invoke the agent

Debug this workflow failure using your favorite Agent CLI and the agentic-workflows prompt.

• Start your agent
• Load the agentic-workflows prompt from .github/agents/agentic-workflows.agent.md or https://github.com/github/gh-aw/blob/main/.github/agents/agentic-workflows.agent.md
• Type debug the agentic workflow ci-postmortem failure in https://github.com/dotnet/macios/actions/runs/26702061058

Tip

Stop reporting this workflow as a failure

To stop a workflow from creating failure issues, set report-failure-as-issue: false in its frontmatter:

safe-outputs:
  report-failure-as-issue: false

Generated from CI Post-Mortem Analysis · ● 3.6M · ◷

• expires on Jun 7, 2026, 3:27 AM UTC