Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Run tests in parallel #184

Open
safesparrow opened this issue Nov 26, 2022 · 3 comments
Open

Run tests in parallel #184

safesparrow opened this issue Nov 26, 2022 · 3 comments

Comments

@safesparrow
Copy link
Contributor

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).

@safesparrow
Copy link
Contributor Author

safesparrow commented Nov 27, 2022

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).
image

@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.

@TheAngryByrd
Copy link
Member

Is there a specific exception coming through for WorkspaceLoaderProjectGraph test? I know ProjectGraph can throw exceptions if another "build" is in progress.

@safesparrow
Copy link
Contributor Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants