microsoft / microsoft/aspire

[CI Failure] Flaky: AppHostServerSessionTests.GetRpcClientAsync_WhenServerExitsBeforeSocketIsAvailable_FailsWithoutWaitingForConnectionTimeout takes longer than expected on Windows runner

Open
#19,150 0 comments 0 reactions 0 assignees View on GitHub
ci-failure-cause quarantined-test 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/31203621605
Build error leg or test failing: Tests / Hosting.Azure / Hosting.Azure (windows-latest) / `Aspire.Cli.Tests.Projects.AppHostServerSessionTests.GetRpcClientAsync_WhenServerExitsBeforeSocketIsAvailable_FailsWithoutWaitingForConnectionTimeout`
Pull request: #19090

## Error Message

```
Expected RPC connection to fail promptly after the server process exited, but it took 00:00:14.9996920. Timing-sensitive assertion on process exit detection under CI load; test file (Aspire.Cli.Tests) not touched by this PR.
```

## Description

Flaky: AppHostServerSessionTests.GetRpcClientAsync_WhenServerExitsBeforeSocketIsAvailable_FailsWithoutWaitingForConnectionTimeout takes longer than expected on Windows runner

**Type**: flaky-test

## Occurrences

| Date | Build | Job | PR |
|------|-------|-----|----|
| 2026-08-07 | [31203621605](https://github.com/microsoft/aspire/actions/runs/31203621605) | Tests / Hosting.Azure / Hosting.Azure (windows-latest) | #19090 |
| 2026-08-11 | [31468992084](https://github.com/microsoft/aspire/actions/runs/31468992084) | Tests / Cli / Cli (windows-latest) | #19215 |
| 2026-08-17 | [32053958727](https://github.com/microsoft/aspire/actions/runs/32053958727) | Tests / Hosting-2 / Hosting-2 (8-core-ubuntu-latest) | #19400 |

Contributor guide

Open the contributing guide

Research direction

Start with Aspire.Cli.Tests.AppHostServerSessionTests.GetRpcClientAsync_WhenServerExitsBeforeSocketIsAvailable and reproduce the timing-sensitive failure on a Windows runner. Review the listed CI runs and the server-exit assertion; done means the test consistently fails promptly after process exit without waiting for the connection timeout.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
cli, testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.