Repository navigation
[CI Failure] Flaky: VS Code extension E2E (Linux, azure-functions) shard fails with generic exit code 1, unrelated to PR changes #19639
Description
Build Information
Build: https://github.com/microsoft/aspire/actions/runs/32781735084
Build error leg or test failing: Tests / Infrastructure / Infrastructure (ubuntu-latest) / VS Code extension E2E (Linux, azure-functions)
Pull request: #19624
Error Message
Process completed with exit code 1. (Run extension E2E tests step failed; job logs unavailable: 'Failed to fetch logs for job'). No TRX test failures extracted. Occurs on 'VS Code extension E2E (Linux, azure-functions)' shard.
Description
Flaky: VS Code extension E2E (Linux, azure-functions) shard fails with generic exit code 1, unrelated to PR changes
Type: flaky-test
Occurrences
| Date | Build | Job | PR |
|---|---|---|---|
| 2026-08-24 | 32781735084 | Tests / Infrastructure / Infrastructure (ubuntu-latest) | #19624 |
| 2026-08-25 | 32791546024 | Tests / Prepare Homebrew installer artifacts / Prepare Homebrew cask | #19430 |
| 2026-08-25 | 32864200821 | Tests / Prepare Homebrew installer artifacts / Prepare Homebrew cask | #19627 |
| 2026-08-26 | 32997866203 | Tests / Run VS Code extension E2E tests / VS Code extension E2E (Windows, apphost-lifecycle-tools) | #19705 |
| 2026-08-26 | 32999137654 | Tests / Azure.Npgsql / Azure.Npgsql (windows-latest) | #19716 |
| 2026-08-27 | 33046510101 | Tests / Build native CLI archive (macOS x64) / Build CLI (osx-x64) | #19709 |
| 2026-08-27 | 33099215991 | Tests / Run VS Code extension E2E tests / VS Code extension E2E (Linux, azure-functions) | #19710 |
| 2026-09-14 | 34858055930 | Tests / Run VS Code extension E2E tests / VS Code extension E2E (Linux, azure-functions) | #19996 |
Activity
adamint commentedon Aug 26, 2026
The concrete failure here was the Azure Functions resource missing its expected HTTPS URL. The shard passed in main runs 32885558008, 32898142217, 32909638198, and 32917733900, and the failure has not repeated. Closing this for now.
radical commentedon Aug 27, 2026
[automated] The
linux/azure-functionsshard is being moved to advisory while this failure is investigated. It appeared in 5 of 7 failed rollingmainCI runs in the latest 36-hour window, repeatedly failing because the Functions resource did not expose the expected HTTPS URL.Advisory does not skip the shard. The test will continue running and uploading diagnostics, and its raw failures will remain visible in the VS Code extension E2E health ledger. A completed Mocha test failure will emit a warning instead of failing the overall CI run. Setup failures, process crashes, signals, timeouts, unexpected exit codes, and cleanup failures remain blocking.
The advisory marker should be removed once the HTTPS endpoint failure is fixed and the shard is stable again.
ci(vscode): Make Azure Functions E2E failures advisory (#19760)
ellahathaway commentedon Sep 10, 2026
Closing as not planned based on the recent VS Code extension E2E health ledger (#19282), observed through 2026-09-10 15:57 UTC. The linux/azure-functions shard recorded 25 passes and one failure on main in the last seven days. That failure was an unrelated setup failure: run 34259343802 failed at Download VSIX because the aspire-extension artifact was missing, before tests ran (https://github.com/microsoft/aspire/actions/runs/34259343802/job/102176916692). No recurrence of the missing-HTTPS-URL assertion was identified in that window. This is not a claim that the underlying race was fixed. The existing advisory configuration is unchanged; restoring blocking status is a separate decision. Reopen if the HTTPS-URL failure recurs.
ellahathaway commentedon Sep 10, 2026
Reopening to correct the previous closure: this issue also tracks removing the temporary advisory mitigation introduced by #19760. That mitigation remains in .github/workflows/extension-e2e-tests.yml and the explicit allowlist in extension/src/test/e2eShardMatrix.test.ts. Recent passing results inform whether it can be removed, but do not complete that follow-up. Keep this issue open until the shard is safely restored to blocking.
ellahathaway commentedon Sep 15, 2026
CI analysis reopened this issue after an Azure Functions Core Tools download failed with HTTP 504 / curl exit code 22, even though Run extension E2E tests was skipped. The analyzer reused the older flaky-test cause based on the shard name rather than the current failure. Closing this issue as it was incorrectly reopened by CI analysis.