microsoft / microsoft/vs-threading
Unstable test: WithCancellationNoDeadlockFromSyncContext_Completed
Open
Nobody has claimed this yet.
test bug
- Dominant language
- C#
- Stars
- 1k
- Forks
- 160
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 28
Description
This test failed in [this build]:
[xUnit.net 00:00:04.0190880] Microsoft.VisualStudio.Threading.Tests.ThreadingToolsTests.WithCancellationNoDeadlockFromSyncContext_Completed [FAIL]
[xUnit.net 00:00:04.0192834] Timed out waiting for completion.
[xUnit.net 00:00:04.0193597] Expected: True
[xUnit.net 00:00:04.0194204] Actual: False
[xUnit.net 00:00:04.0205442] Stack Trace:
[xUnit.net 00:00:04.0274265] C:\projects\vs-threading\src\Microsoft.VisualStudio.Threading.Tests\ThreadingToolsTests.cs(303,0): at Microsoft.VisualStudio.Threading.Tests.ThreadingToolsTests.WithCancellationSyncBlock(Boolean simulateCancellation)
Failed Microsoft.VisualStudio.Threading.Tests.ThreadingToolsTests.WithCancellationNoDeadlockFromSyncContext_Completed
Error Message:
Timed out waiting for completion.
Expected: True
Actual: False
Stack Trace:
at Microsoft.VisualStudio.Threading.Tests.ThreadingToolsTests.WithCancellationSyncBlock(Boolean simulateCancellation) in C:\projects\vs-threading\src\Microsoft.VisualStudio.Threading.Tests\ThreadingToolsTests.cs:line 303
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the failing WithCancellationNoDeadlockFromSyncContext_Completed test in ThreadingToolsTests.cs, especially the WithCancellationSyncBlock failure at line 303, and run the test to reproduce the timeout. Done means the test completes reliably without the reported timeout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100