ci(vscode): Keep CI green when Azure Functions E2E flakes - #19760
Merged
Ankit Jain (radical) merged 1 commit intoSep 1, 2026
Merged
Conversation
The Linux Azure Functions E2E shard intermittently fails because the Functions resource does not expose its expected HTTPS URL. This failure caused five of seven red main CI runs in a recent 36-hour window. Keep running the shard and uploading diagnostics, but treat completed Mocha test failures as advisory. Setup, process, timeout, unexpected exit, and cleanup failures remain blocking. Update the explicit advisory-shard allowlist so the mitigation remains reviewable. Refs microsoft#19639 Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 8f5ea755-6426-482e-a619-6c65f8924f71
Contributor
|
🚀 Dogfood this PR with:
curl -fsSL https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 19760Or
iex "& { $(irm https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 19760" |
Contributor
There was a problem hiding this comment.
Pull request overview
Makes Linux Azure Functions E2E assertion failures advisory while preserving blocking behavior for infrastructure and cleanup failures.
Changes:
- Adds issue #19639 to the Azure Functions shard’s advisory configuration.
- Updates the explicit advisory-shard allowlist test.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
.github/workflows/extension-e2e-tests.yml |
Marks the Linux Azure Functions shard advisory. |
extension/src/test/e2eShardMatrix.test.ts |
Tracks the advisory shard and issue explicitly. |
💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.
Ankit Jain (radical)
added
the
area-engineering-systems
Ankit Jain (radical)
marked this pull request as ready for review
August 27, 2026 22:07
Ankit Jain (radical)
requested review from
Adam Ratzman (adamint) and
Ella Hathaway (ellahathaway)
as code owners
August 27, 2026 22:07
Ankit Jain (radical)
changed the title
Ankit Jain (radical)
enabled auto-merge (squash)
August 27, 2026 23:08
Adam Ratzman (adamint)
approved these changes
Sep 1, 2026
50 tasks
This was referenced Sep 1, 2026
Contributor
|
🔍 CI Failure Analysis: Transient Infrastructure Failure The CI build failed due to transient infrastructure issues. Failed jobs:
If a rerun was not already requested automatically, visit the workflow run page to rerun the failed jobs manually. |
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
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.
Description
Rolling
mainCI stays red when the Linux Azure Functions extension E2E shard intermittently fails with:Only 3 of 11 rolling
mainruns passed during the latest 36-hour investigation window. This shard appeared in five of the seven failed runs, making it the dominant recurring cause of red rolling CI.This change keeps the shard running and uploading diagnostics, but reports completed Mocha test failures as advisory warnings so this known flake no longer fails the overall CI run. Setup failures, process crashes, signals, timeouts, unexpected exit codes, and cleanup failures remain blocking.
This preserves coverage and failure evidence instead of disabling the shard entirely. The explicit advisory-shard allowlist keeps the mitigation deliberate and reviewable.
Addresses #19639
Checklist
<remarks />and<code />elements on your triple slash comments?