[CI Failure] VS Code extension E2E tests fail with unavailable logs and generic exit code 1, unrelated to PR changes

[github-actions]

Build Information

Build: https://github.com/microsoft/aspire/actions/runs/32704259463
Build error leg or test failing: Tests / Run VS Code extension E2E tests / VS Code extension E2E (Linux, workspace-target-proof) / VS Code extension E2E (matrix shards, e.g. workspace-target-proof / edge-cases)
Pull request: #19520

Error Message

Run extension E2E tests step fails with 'Process completed with exit code 1.' Job logs could not be fetched ('Failed to fetch logs for job'). Occurs on PRs unrelated to the extension codebase, similar to known extension-e2eshardmatrix-windows-flaky pattern.

Description

VS Code extension E2E tests fail with unavailable logs and generic exit code 1, unrelated to PR changes

Type: flaky-test

Occurrences

Showing 31 most recent of 31 occurrences.

Date	Build	Job	Context
2026-08-24	32704259463	Tests / Run VS Code extension E2E tests / VS Code extension E2E (Linux, workspace-target-proof)	#19520
2026-09-13	34740415883	Tests / Run VS Code extension E2E tests / VS Code extension E2E (Linux, browser-debugger)	#20067
2026-09-13	34740434278	Tests / No-package tests (regular, Infrastructure.Tests, Infrastructure, Infrastructure, tests/Infrastruc... / Infrastructure (ubuntu-latest)	#20020
2026-09-13	34747853466	Tests / No-package tests (regular, Aspire.Cli.Tests, Cli, Cli, tests/Aspire.Cli.Tests/Aspire.Cli.Tests.cs... / Cli (macos-latest)	#20031
2026-09-13	34783506552	Tests / Package tests - Windows (class, Aspire.Templates.Tests, Templates-XUnit_Default_NewUpAndBuildSupportProjectTemplatesTests (windows-latest))	#20021
2026-09-14	34790579218	Tests / No-package tests (regular, Aspire.Cli.Tests, Cli, Cli, tests/Aspire.Cli.Tests/Aspire.Cli.Tests.cs... / Cli (macos-latest)	#20079
2026-09-14	34791816809	Tests / No-package tests (regular, Aspire.Cli.Tests, Cli, Cli, tests/Aspire.Cli.Tests/Aspire.Cli.Tests.cs... / Cli (macos-latest)	#20099
2026-09-14	34806422379	Tests / Run VS Code extension E2E tests / VS Code extension E2E (Windows, winui-debug)	#19882
2026-09-14	34808457010	Tests / Polyglot SDK Validation / TypeScript SDK Validation (Node 24.x)	#20084
2026-09-14	34815567672	Tests / Run VS Code extension E2E tests / VS Code extension E2E (Windows, browser-debugger)	#18763
2026-09-14	34858055930	Tests / Run VS Code extension E2E tests / VS Code extension E2E (Windows, browser-debugger)	#19996
2026-09-14	34863279227	Tests / Run VS Code extension E2E tests / VS Code extension E2E (Linux, browser-debugger)	#19814
2026-09-15	34941224700	Tests / Run VS Code extension E2E tests / VS Code extension E2E (Windows, browser-debugger)	#20011
2026-09-15	35023188186	Tests / Run VS Code extension E2E tests / VS Code extension E2E (Windows, browser-debugger)	#20146
2026-09-16	35036422457	Tests / Run VS Code extension E2E tests / VS Code extension E2E (Windows, browser-debugger)	#19675
2026-09-16	35037910646	Tests / Run VS Code extension E2E tests / VS Code extension E2E (Windows, browser-debugger)	#19848
2026-09-16	35053406342	Tests / Run VS Code extension E2E tests / VS Code extension E2E (Windows, browser-debugger)	#20152
2026-09-16	35055620862	Tests / Run VS Code extension E2E tests / VS Code extension E2E (Windows, browser-debugger)	#20082
2026-09-17	35274272340	Tests / Run VS Code extension E2E tests / VS Code extension E2E (Windows, browser-debugger)	#20157
2026-09-17	35275989131	Tests / Run VS Code extension E2E tests / VS Code extension E2E (Windows, browser-debugger)	#20203
2026-09-18	35313069592	Tests / Run VS Code extension E2E tests / VS Code extension E2E (Linux, browser-debugger)	#20220
2026-09-18	35366726944	Tests / Run VS Code extension E2E tests / VS Code extension E2E (Windows, browser-debugger)	#20195
2026-09-18	35373021439	Tests / Run VS Code extension E2E tests / VS Code extension E2E (Linux, browser-debugger)	#20148
2026-09-18	35377484081	Tests / Run VS Code extension E2E tests / VS Code extension E2E (Windows, browser-debugger)	#20156
2026-09-19	35407089360	Tests / Run VS Code extension E2E tests / VS Code extension E2E (Windows, browser-debugger)	#20244
2026-09-21	35562512049	Tests / Run VS Code extension E2E tests / VS Code extension E2E (Windows, browser-debugger)	#1391
2026-09-21	35624998816	Tests / Run VS Code extension E2E tests / VS Code extension E2E (Windows, browser-debugger)	#20032
2026-09-21	35634736322	Tests / Run VS Code extension E2E tests / VS Code extension E2E (Windows, browser-debugger)	#20279
2026-09-22	35676789810	Tests / Run VS Code extension E2E tests / VS Code extension E2E (Windows, browser-debugger)	#20296
2026-09-22	35756256834	Tests / Run VS Code extension E2E tests / VS Code extension E2E (Windows, browser-debugger)	#20131
2026-09-23	35819211421	Tests / Run VS Code extension E2E tests / VS Code extension E2E (Windows, browser-debugger)	main

[adamint]

This is the same Linux workspace-target-proof failure tracked in #19597, with no distinct failure evidence once the diagnostics were available. Closing as a duplicate.

[ellahathaway]

I investigated the reopened occurrences and found that #19618 is grouping different failures under the same generic CI signature; the latest occurrence is not a recurrence of #19597.

• [CI Failure] Flaky: VS Code extension E2E (Linux, workspace-target-proof) shard fails with generic exit code 1, unrelated to PR changes #19597’s Linux workspace-target-proof failure had concrete diagnostics: the workspace wrapper ran new from the wrong folder. That shard then passed in main runs 32898142217, 32909638198, and 32917733900.
• The latest listed occurrence, main run 35819211421, is Windows browser-debugger. Its failed test is maps managed Edge debugging to the C# Blazor WebAssembly attach contract (7 of 8 tests passed).
• The job annotation is still only Process completed with exit code 1, but the diagnostics upload succeeded. The artifact shows VS Code logged Invalid debug adapter, while the WebAssembly bridge repeatedly failed to connect to the browser DevTools endpoint with socket error 10061 (connection refused). AppHost/resource teardown completed successfully.

This points to a browser-debugger/DevTools proxy or debug-adapter startup failure, not the old workspace-target wrapper bug. The generic-exit-code occurrence grouping is too broad; these should be tracked by shard/test (or the automation should preserve and use the uploaded diagnostics when grouping failures).

Run: https://github.com/microsoft/aspire/actions/runs/35819211421