Threadpool test CooperativeBlockingCanCreateThreadsFaster failing on Mac #66852
Labels
Comments
agocke
added
area-System.Threading
blocking-clean-ci
|
Tagging subscribers to this area: @mangod9 Issue DetailsRunfo Tracking Issue: Threadpool test CooperativeBlockingCanCreateThreadsFaster failing on Mac
Build Result Summary
|
|
@mangod9 This test has failed the last three rolling builds, so I think we should consider disabling in MacOS if the failure cause isn't obvious |
|
Test was disabled by #66988, so this is no longer blocking |
agocke
removed
the
blocking-clean-ci
ghost
added
the
in-pr
agocke
added
the
disabled-test
ghost
removed
the
in-pr
kouvel
added a commit
to kouvel/runtime
that referenced
this issue
Mar 31, 2022
- The test verifies that cooperative blocking in `Task.Wait()` causes threads to be injected quickly enough that it does not time out due to starvation - Cooperative blocking checks memory usage and limit, and beyond a threshold of memory usage does not inject threads quickly - Following a build of the runtime repo, there are several `dotnet` processes that remain running, each using several 100s of MBs and one using ~1.3 GB of memory - If the test runs soon after the build, before those processes exit, it's possible for the reported memory usage to be high enough that the test would fail - Added a config var to ignore memory usage and used it in the test Fixes dotnet#66852
ghost
added
the
in-pr
kouvel
added a commit
that referenced
this issue
Apr 26, 2022
- The test verifies that cooperative blocking in `Task.Wait()` causes threads to be injected quickly enough that it does not time out due to starvation - Cooperative blocking checks memory usage and limit, and beyond a threshold of memory usage does not inject threads quickly - Following a build of the runtime repo, there are several `dotnet` processes that remain running, each using several 100s of MBs and one using ~1.3 GB of memory - If the test runs soon after the build, before those processes exit, it's possible for the reported memory usage to be high enough that the test would fail - Added a config var to ignore memory usage and used it in the test Fixes #66852
ghost
removed
the
in-pr
ghost
locked as resolved and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Runfo Tracking Issue: Threadpool test CooperativeBlockingCanCreateThreadsFaster failing on Mac
Build Result Summary
The text was updated successfully, but these errors were encountered: