You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Running tests takes a long time, because they run in sequence.
Describe the solution you'd like
I would like the tests to be run in parallel.
Additional context
I tried this and most tests work (and fast), but some are unable to load the projects when running alongside other tests.
I'm trying to find the root cause of that.
This also requires using unique test directories for each test (currently they are not).
The text was updated successfully, but these errors were encountered:
So one type of tests that fails when run in parallel is the load project from disk everytime but only the one that uses WorkspaceLoaderProjectGraph. On the screenshot below the middle test is the one using project graph, while first and last use WorkspaceLoader (I changed the names to force a certain order of test scheduling (which might have been useless anyway).
@baronfel Do you have any idea what about this type of test would make it susceptible to other tests' side effects?
I can't quite figure out what's different about running in parallel.
I already use unique test directories.
As far as I can see we already use a single tools path for all tests, ie. we don't re-init ProjInfo for each individual proejct.
How can I see those exceptions? What I'm getting is no projects are loaded so the test fails later on. I guess I should generate a binlog in case something is wrong in msbuild.
Is your feature request related to a problem? Please describe.
Running tests takes a long time, because they run in sequence.
Describe the solution you'd like
I would like the tests to be run in parallel.
Additional context
I tried this and most tests work (and fast), but some are unable to load the projects when running alongside other tests.
I'm trying to find the root cause of that.
This also requires using unique test directories for each test (currently they are not).
The text was updated successfully, but these errors were encountered: