TeamCity runs paralell.For loop serially after upgrade of TeamCity and MSBuild
Completed
A few of our NUnit tests runs much slower after we upgraded to 2019.1.2 (build 66342) and to MSBuild 2019.
It seems the problem is that
Parallel.For
is not run in parallel. We can show this by running the same code with a for-loop and comparing computation-times.
Is there any settings we are missing?
Please sign in to leave a comment.
For reference of anybody who might stumble across this thread, this was handled in our issue tracker here: https://youtrack.jetbrains.com/issue/TW-63374. The issue seemed to be related to the OS version.