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.

Sign up for GitHub

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

Jump to bottom

[Test] Run tests in parallel #10640

Open
2 tasks
f-alizada opened this issue Sep 10, 2024 · 2 comments
Open
2 tasks

[Test] Run tests in parallel #10640

f-alizada opened this issue Sep 10, 2024 · 2 comments
Labels
Area: Our Own Build Problems affecting the build or build infrastructure of the MSBuild repo itself. Area: Tests Priority:3 Work that is nice to have triaged

Comments

@f-alizada
Copy link
Contributor

Context

Current setup of our test runner turns off the parallelization.

msbuild/src/Shared/UnitTests/xunit.runner.json

Lines 6 to 7 in 371d00f

"maxParallelThreads": 1,
"parallelizeTestCollections": false,

Goal

Decrease the time spent on test by leveraging the parallelization in test runs.

  • Determine the amount of time spent on test per run
  • Calculate the possible wins by running in parallel
@f-alizada f-alizada added Area: Our Own Build Problems affecting the build or build infrastructure of the MSBuild repo itself. Area: Tests Priority:3 Work that is nice to have labels Sep 10, 2024
@f-alizada f-alizada changed the title Run tests in parallel [Test] Run tests in parallel Sep 10, 2024
@rainersigwald
Copy link
Member

rainersigwald commented Sep 10, 2024 •
edited
Loading

IMO it'd be better to tackle this by increasing assembly-level parallelization rather than within-assembly. Arcade doesn't handle assembly-level scheduling well as I recall.

@AR-May
Copy link
Member

AR-May commented Sep 17, 2024

That would be quite a huge refactoring of the test classes. So many of them does count on absence of parallelization.

@AR-May AR-May added the triaged label Sep 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area: Our Own Build Problems affecting the build or build infrastructure of the MSBuild repo itself. Area: Tests Priority:3 Work that is nice to have triaged
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@rainersigwald @AR-May @f-alizada