microsoft / microsoft/aspire

[CI Failure] VS Code extension VSIX packaging fails on Windows unit test job, cascading to all E2E test artifact downloads

Open
#19,745 1 comment 0 reactions 0 assignees View on GitHub
area-vscode ci-failure-cause
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/33086828076
Build error leg: Tests / Run VS Code extension unit tests (Windows)
Pull request: #19730

## Error Message

```
No files were found with the provided path: extension/out/aspire-extension.vsix. No artifacts will be uploaded. Failed steps: Install dependencies, Package VSIX, Assert E2E VSIX contains bridge, Package production VSIX, Assert production VSIX excludes bridge. Job logs unavailable ('Failed to fetch logs for job'). PR only modifies src/Aspire.Cli/Telemetry/CodingAgentDetector.cs and its test, unrelated to VS Code extension build.
```

## Description

VS Code extension VSIX packaging fails on Windows unit test job, cascading to all E2E test artifact downloads

**Type**: infra-failure

## Occurrences

| Date | Build | Job | PR |
|------|-------|-----|----|
| 2026-08-27 | [33086828076](https://github.com/microsoft/aspire/actions/runs/33086828076) | Tests / Run VS Code extension unit tests (Windows) | #19730 |
| 2026-09-08 | [34259343802](https://github.com/microsoft/aspire/actions/runs/34259343802) | Tests / Run VS Code extension unit tests (Windows) / Run VS Code extension unit tests (Windows) | #17742 |

Contributor guide

Open the contributing guide

Research direction

Start with the Tests / Run VS Code extension unit tests (Windows) job and its Install dependencies, Package VSIX, and assertion steps. Check why extension/out/aspire-extension.vsix is not produced or found; done means both VSIX packaging assertions pass and the E2E VSIX artifacts are uploaded for download.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, vscode
Domain
ci-cd, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.