[CI Failure] Flaky: VS Code extension unit tests job fails intermittently on Windows with generic exit code 1 and no retrievable logs

[github-actions]

Build Information

Build: https://github.com/microsoft/aspire/actions/runs/31556011348
Build error leg: Tests / Run VS Code extension unit tests (Windows)
Pull request: #19232

Error Message

Process completed with exit code 1. (Job logs unavailable: 'Failed to fetch logs for job'). No TRX test failures extracted. Occurs on the 'Run VS Code extension unit tests (Windows)' job unrelated to PR changes touching only Aspire.Cli DotNet path resolution code.

Description

Flaky: VS Code extension unit tests job fails intermittently on Windows with generic exit code 1 and no retrievable logs

Type: flaky-test

Occurrences

Date	Build	Job	PR
2026-08-12	31556011348	Tests / Run VS Code extension unit tests (Windows)	#19232
2026-09-11	34564571207	Tests / Run VS Code extension unit tests (Windows) / Run VS Code extension unit tests (Windows)	#20057
2026-09-14	34858055930	Tests / Run VS Code extension unit tests (Windows) / Run VS Code extension unit tests (Windows)	#19996
2026-09-22	35683878838	Tests / Run VS Code extension unit tests (Windows) / Run VS Code extension unit tests (Windows)	#20289

[adamint]

This was the same deterministic allowlist mismatch as #19265, not an independent flaky failure. #19267 fixed it, and the current main extension unit suite passes. I consolidated the remaining E2E gate work and current-main investigation in #19282. Closing this as completed.

[ellahathaway]

The tracking issue remains valid, but the original classification is stale.

The August failure was the deterministic E2E matrix allowlist mismatch fixed by #19267. The later occurrences are separate failures in the same Windows VS Code extension unit-test job:

• September 11, run 34564571207: the Run tests step failed while downloading/unzipping VS Code 1.131.0 with Error: aborted.
• September 14, run 34858055930: the same job and step failed.
• September 22, run 35683878838: the same job and step failed.

This supports keeping the issue open as an intermittent Windows CI/setup failure, but the body should be updated to distinguish these failures from the resolved allowlist mismatch and to investigate VS Code download/setup reliability rather than treating them as the same test failure.

[ellahathaway]

Additional log detail: the September 14 run reported a Windows keytar optional-dependency install failure and then exhausted transient retries before exiting 1. The September 22 run likewise exhausted transient retries before exiting 1. These are consistent with intermittent Windows dependency/setup instability, not the original matrix allowlist assertion.