microsoft / microsoft/aspire

[CI Failure] Flaky: VS Code extension E2E (Windows, tree-actions) shard fails with generic exit code 1, unrelated to PR changes

Open
#20,103 0 comments 0 reactions 0 assignees View on GitHub
ci-failure-cause test-failure
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/34795444609
Build error leg or test failing: Tests / Run VS Code extension E2E tests / VS Code extension E2E (Windows, dynamic-debug-configuration) / `VS Code extension E2E (Windows, tree-actions)`
Pull request: #20062

## 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.
```

## Description

Flaky: VS Code extension E2E (Windows, tree-actions) shard fails with generic exit code 1, unrelated to PR changes

**Type**: flaky-test

## Occurrences

| Date | Build | Job | PR |
|------|-------|-----|----|
| 2026-09-14 | [34795444609](https://github.com/microsoft/aspire/actions/runs/34795444609) | Tests / Run VS Code extension E2E tests / VS Code extension E2E (Windows, dynamic-debug-configuration) | #20062 |

Contributor guide

Open the contributing guide

Research direction

Start with build 34795444609 and the Tests / Run VS Code extension E2E tests workflow, focusing on the Windows tree-actions shard and its failed Run extension E2E tests step. The reported job logs are unavailable and no TRX failures were extracted, so done means identifying and addressing the flaky failure and confirming the shard passes reliably.

Written by the indexing model from the issue text.

Assessment

Tech stack
vscode
Domain
ci-cd, testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.