[CI Failure] Flaky: VS Code extension E2E (Linux/Windows, launch-profiles) shard fails with generic exit code 1, unrelated to PR changes
- Dominant language
- C#
- Stars
- 6.3k
- Forks
- 991
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 196
Description
## Build Information
Build: https://github.com/microsoft/aspire/actions/runs/33811778450
Build error leg or test failing: Tests / No-package tests (regular, Aspire.Azure.Npgsql.EntityFrameworkCore.PostgreSQL.Tests...) / Azure.Npgsql.EntityFrameworkCore.PostgreSQL (windows-latest) / `VS Code extension E2E (launch-profiles)`
Pull request: #19918
## 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 'launch-profiles' shard unrelated to PR changes touching only .github/extensions/aspire-team-app scripts.
```
## Description
Flaky: VS Code extension E2E (Linux/Windows, launch-profiles) shard fails with generic exit code 1, unrelated to PR changes
**Type**: flaky-test
## Occurrences
| Date | Build | Job | PR |
|------|-------|-----|----|
| 2026-09-03 | [33811778450](https://github.com/microsoft/aspire/actions/runs/33811778450) | Tests / No-package tests (regular, Aspire.Azure.Npgsql.EntityFrameworkCore.PostgreSQL.Tests...) / Azure.Npgsql.EntityFrameworkCore.PostgreSQL (windows-latest) | #19918 |
| 2026-09-04 | [33821649109](https://github.com/microsoft/aspire/actions/runs/33821649109) | Tests / Polyglot SDK Validation / TypeScript SDK Validation (Node 24.x) | #19910 |
| 2026-09-11 | [34553168379](https://github.com/microsoft/aspire/actions/runs/34553168379) | Tests / No-package tests (regular, Aspire.StackExchange.Redis.Tests, StackExchange.Redis, StackExchange.R... / StackExchange.Redis (windows-latest) | #20054 |
Contributor guide
Research direction
Start with the linked workflow run and the VS Code extension E2E (launch-profiles) shard, then compare the three listed occurrences across Linux and Windows jobs. Job logs are unavailable in the report, so determine the underlying failure before changing anything. Done means the flaky cause is addressed and the launch-profiles shard passes reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- ci-cd, devtools, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100