[CI Failure] Flaky: ResourceLoggerForwarderServiceTests.ExecuteDoesNotThrowOperationCanceledWhenAppStoppingTokenSignaled times out intermittently on Windows
- 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/30416905407
Build error leg or test failing: Tests / Hosting.Testing / Hosting.Testing (windows-latest) / `Aspire.Hosting.Testing.Tests.ResourceLoggerForwarderServiceTests.ExecuteDoesNotThrowOperationCanceledWhenAppStoppingTokenSignaled`
Pull request: #18561
## Error Message
```
System.TimeoutException : The operation has timed out.
at Aspire.Hosting.Testing.Tests.ResourceLoggerForwarderServiceTests.ExecuteDoesNotThrowOperationCanceledWhenAppStoppingTokenSignaled() in /_/tests/Aspire.Hosting.Testing.Tests/ResourceLoggerForwarderServiceTests.cs:line 59
```
## Description
Flaky: ResourceLoggerForwarderServiceTests.ExecuteDoesNotThrowOperationCanceledWhenAppStoppingTokenSignaled times out intermittently on Windows
**Type**: flaky-test
## Occurrences
| Date | Build | Job | PR |
|------|-------|-----|----|
| 2026-07-29 | [30416905407](https://github.com/microsoft/aspire/actions/runs/30416905407) | Tests / Hosting.Testing / Hosting.Testing (windows-latest) | #18561 |
Contributor guide
Research direction
Start with tests/Aspire.Hosting.Testing.Tests/ResourceLoggerForwarderServiceTests.cs at line 59 and the named test, then reproduce it on the windows-latest test job. Review the timeout around app-stopping token signaling. Done means the test completes reliably on Windows and continues verifying that Execute does not throw OperationCanceledException.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100