Fix Helix file URIs for subdirectory artifacts (xharness-output)#124126
Merged
Fix Helix file URIs for subdirectory artifacts (xharness-output)#124126
Conversation
Workaround for dotnet/dnceng#6072: Helix API returns incorrect file URIs for files uploaded from subdirectories (e.g., xharness-output/testResults.xml). Rebuild URIs from the FileName field which correctly includes the path.
github-actions
bot
added
the
needs-area-label
Member
Author
|
cc @akoeplinger @dotnet/dnceng — this is a client-side workaround for dotnet/dnceng#6072 (Helix file URIs broken for subdirectory artifacts like xharness-output). Can be removed once the API fix lands. |
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the AzDO Helix failures skill to work around a Helix API issue where artifact links for files uploaded from subdirectories (e.g., xharness-output/...) are returned with incorrect URIs, causing 404s when followed.
Changes:
- Add a URI “fixup” step in
Get-HelixWorkItemDetailsto rebuild file URIs based onFileNamewhen the file is under a subdirectory. - Document the known Helix API URI bug and the script workaround in
helix-artifacts.md.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
.github/skills/azdo-helix-failures/scripts/Get-HelixFailures.ps1 |
Rebuilds Helix artifact URIs for subdirectory file paths to avoid broken links. |
.github/skills/azdo-helix-failures/references/helix-artifacts.md |
Adds documentation about the Helix API bug affecting subdirectory artifact URIs. |
.github/skills/azdo-helix-failures/scripts/Get-HelixFailures.ps1
Outdated
Show resolved
Hide resolved
lewing
added
arch-arm64
area-skills
lewing
force-pushed
the
lewing/helix-xharness-uri-fix
branch
from
ec1d152 to
da96dd9
Compare
.github/skills/azdo-helix-failures/scripts/Get-HelixFailures.ps1
Outdated
Show resolved
Hide resolved
- Update SKILL.md description to cover CI status checks, not just failures - Add trigger phrases: 'is CI passing', 'build status', 'ready to merge' - Add job summary in build output (e.g., '143 total: 142 passed, 1 failed') - Improve no-build-found message to explain CI hasn't been triggered
lewing
force-pushed
the
lewing/helix-xharness-uri-fix
branch
from
da96dd9 to
69319e2
Compare
steveisok
approved these changes
Feb 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two improvements to the Helix CI analysis skill:
1. Fix Helix file URIs for subdirectory artifacts (xharness-output)
Workaround for dotnet/dnceng#6072 — Helix API returns incorrect URIs for files in subdirectories (e.g.,
xharness-output/wasm-console.log). The API strips the path prefix, resulting in 404s. This rebuilds the correct URI from theFileNamewhen it contains/.2. Broaden skill to general CI status analysis
The skill was described as "failure analysis" only, which meant it wasn't used when checking general CI status (e.g., "is CI passing?", "what's the build status?"). Changes:
Jobs: 143 total (142 passed, 1 failed)) instead of only showing failed job countBefore:
After: