[Failing test]: Aspire.Hosting.Maui.Tests.MauiBuildQueueTests.ReleaseSemaphoreAfterLaunchAsync\_SkipsReplayStateAndReleasesOnStableState
- 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/28395604383
Build error leg or test failing: Aspire.Hosting.Maui.Tests.MauiBuildQueueTests.ReleaseSemaphoreAfterLaunchAsync\_SkipsReplayStateAndReleasesOnStableState
Logs: [Tests / Hosting.Maui / Hosting.Maui \(windows-latest\)](https://github.com/microsoft/aspire/actions/runs/28395604383/job/84133954423)
### Fill in the error message template
## Error Message
Fill the error message using [step by step known issues guidance](https://github.com/dotnet/arcade/blob/main/Documentation/Projects/Build%20Analysis/KnownIssueJsonStepByStep.md).
```json
{
"ErrorMessage": "System.TimeoutException : The operation has timed out.",
"ErrorPattern": "",
"BuildRetry": false,
"ExcludeConsoleLog": false
}
```
### Error details
```yml
Error Message: System.TimeoutException : The operation has timed out.
Stack Trace:
at Aspire.Hosting.Maui.Tests.MauiBuildQueueTests.ReleaseSemaphoreAfterLaunchAsync_SkipsReplayStateAndReleasesOnStableState() in D:\a\aspire\aspire\tests\Aspire.Hosting.Maui.Tests\MauiBuildQueueTests.cs:line 663
at Aspire.Hosting.Maui.Tests.MauiBuildQueueTests.ReleaseSemaphoreAfterLaunchAsync_SkipsReplayStateAndReleasesOnStableState() in D:\a\aspire\aspire\tests\Aspire.Hosting.Maui.Tests\MauiBuildQueueTests.cs:line 664
--- End of stack trace from previous location ---
```
Standard Output
_No content captured._
📊 **[View CI Failure Report](https://github.com/microsoft/aspire/issues/18560#issuecomment-4836537991)**
Contributor guide
Research direction
Start with tests/Aspire.Hosting.Maui.Tests/MauiBuildQueueTests.cs at lines 663-664 and run ReleaseSemaphoreAfterLaunchAsync_SkipsReplayStateAndReleasesOnStableState on Windows. Inspect the timeout and surrounding test behavior to identify why the semaphore is not released as expected. Done means the test completes reliably without System.TimeoutException.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- mobile-dev, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100