microsoft / microsoft/vs-threading

Unstable test: WithCancellationNoDeadlockFromSyncContext_Canceled

Open
#267 0 comments 0 reactions 0 assignees View on GitHub

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 on appveyor, with this output:

WithCancellationNoDeadlockFromSyncContext_Canceled [FAIL]
      Timed out waiting for completion.
      Expected: True
      Actual:   False
      Stack Trace:
        src\Microsoft.VisualStudio.Threading.Tests\ThreadingToolsTests.cs(0,0): at Microsoft.VisualStudio.Threading.Tests.ThreadingToolsTests.WithCancellationSyncBlock(Boolean simulateCancellation)
        src\Microsoft.VisualStudio.Threading.Tests\ThreadingToolsTests.cs(228,0): at Microsoft.VisualStudio.Threading.Tests.ThreadingToolsTests.WithCancellationNoDeadlockFromSyncContext_Canceled()

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in src/Microsoft.VisualStudio.Threading.Tests/ThreadingToolsTests.cs at WithCancellationNoDeadlockFromSyncContext_Canceled and the WithCancellationSyncBlock helper referenced by the failure. Reproduce the timeout and inspect the synchronization and cancellation behavior; done means the test completes reliably instead of timing out.

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
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.