Uh oh!
There was an error while loading. Please reload this page.
Try to fix a time-sensitive thread pool test - #66765
Conversation
ghost
commented
Mar 17, 2022
Tagging subscribers to this area: @mangod9 Issue DetailsI guess the test may occasionally time out if it's running in parallel with other tests, depending on what those other tests are doing. Subscribed to thread adjustment events to see if progress is being made to extend the timeout. Hopefully fixes #66755
|
am11
commented
Mar 19, 2022
If parallelization is the root-cause of failure, there is
(requires <Compile Include="$(CommonTestPath)TestUtilities\System\DisableParallelizationPerAssembly.cs" /> in csproj) |
kouvel
commented
Mar 22, 2022
Does that disable parallelization only for this test assembly, or does it also disable parallelization between tests from different assemblies? |
am11
commented
Mar 22, 2022
I am not sure but I think on helix, we only execute one test assembly at a time? @adamsitnik might know the definite answer. |
adamsitnik
commented
Mar 22, 2022
Afaik this is true (cc @ericstj who is our ultimate source of truth).
by using it it's ensured that all tests in given assembly are run sequentially. DisableParallelization runs all other tests in parallel first, and then at the end sequentially tests from types marked with this attribute (this is typically what I am using). |
|
hoyosjs
commented
Mar 22, 2022
Helix assemblies for libraries do run on a project basis: https://helix.dot.net/api/jobs/f8d1561b-e515-4958-8114-6d2a0900b0de/workitems?api-version=2019-06-17 each one of those runs separately. |
I guess the test may occasionally time out if it's running in parallel with other tests, depending on what those other tests are doing. Subscribed to thread adjustment events to see if progress is being made to extend the timeout. Hopefully fixes#66755
ericstj
commented
Mar 22, 2022
Ha! I'm not the source of truth -- the source is. I just read it. It can change at any time so I go back and re-read it. Sometimes I don't read the source and instead read the test logs if I don't trust my eyeball-debugger. cc @dotnet/runtime-infrastructure In libraries we don't parallelize at the assembly level. Each test assembly gets launched once and helix only runs one job at a time on the machine. You can examine how that works here: runtime/eng/testing/tests.targets Line 104 in 96ef47b https://github.com/dotnet/runtime/search?q=RunScriptCommand The coreclr tests are a little different. They intentionally parallelize (and that actually has caused problems). You can see that here: runtime/src/tests/Common/testgrouping.proj Lines 284 to 303 in d8f8527 |
kouvel
commented
Mar 22, 2022
Thanks all! I'll try disabling parallelization for this test. |
Still failing and appears to not be a parallelization issue. I can repro the issue on the latest macOS, seems to be an issue with |
I guess the test may occasionally time out if it's running in parallel with other tests, depending on what those other tests are doing. Subscribed to thread adjustment events to see if progress is being made to extend the timeout.
Hopefully fixes#66852