Avoid stale AzDO retry failure annotations - #10456
Conversation
Report intermediate acceptance-test failures as warnings so successful retries do not leave the test step marked with failed annotations. Final retry failures remain enforced by the process exit code and TRX publication. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 6e336030-19fa-4526-8bf3-aca348e24bdd
There was a problem hiding this comment.
Pull request overview
Configures retry-enabled MTP acceptance tests to avoid stale Azure DevOps failure annotations.
Changes:
- Emits Azure DevOps annotations as warnings.
- Retains final failure signaling through exit codes and TRX results.
Show a summary per file
| File | Description |
|---|---|
test/IntegrationTests/Microsoft.Testing.Platform.Acceptance.IntegrationTests/Microsoft.Testing.Platform.Acceptance.IntegrationTests.csproj |
Adds warning severity for Azure DevOps reporting. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 0
- Review effort level: Balanced
|
Caution agentic threat detected DetailsPotential security threats were detected in the agent output. Review the workflow run logs for details. 🧵 Parallel-safety audit — PR #10456Nothing audited here touches process-global state, shared filesystem paths, or Nothing to flag for parallel-safety. Re-run with
|
Summary
Root cause
--report-azdoemits an irreversible##vso[task.logissue type=error]as soon as an attempt fails. The retry orchestrator can later recover the test, but Azure DevOps retains the initial error annotation even though the final retry summary, exit code, and Tests tab are green.Validation
Microsoft.Testing.Platform.Acceptance.IntegrationTests.csprojin Release--report-azdo-severity warning