microsoft / microsoft/vs-threading
Unstable test: NoLeakForContestedRequests_ThatAreCanceled
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1k
- Forks
- 160
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 28
Description
The test failed in this build:
Leaks observed in every iteration.
Expected: True
Actual: False
at Microsoft.VisualStudio.Threading.Tests.TestBase.<CheckGCPressureAsync>d__19.MoveNext() in d:\a\1\s\src\Microsoft.VisualStudio.Threading.Tests\TestBase.cs:line 238
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Threading.Tests.AsyncSemaphoreTests.<NoLeakForContestedRequests_ThatAreCanceled>d__23.MoveNext() in d:\a\1\s\src\Microsoft.VisualStudio.Threading.Tests\AsyncSemaphoreTests.cs:line 410
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
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 AsyncSemaphoreTests.cs at line 410 and TestBase.cs at line 238, using the linked build failure as context. Run NoLeakForContestedRequests_ThatAreCanceled repeatedly to reproduce the leak failure. Done means the test reliably passes without reporting leaks.
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