-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
use TestDisableParallelization property to disable parallel test execution #62133
Conversation
Tagging subscribers to this area: @Anipik, @safern, @ViktorHofer Issue DetailsIt's defined in: runtime/eng/testing/runsettings.targets Lines 30 to 42 in c66fa99
and I've tested that it works as expected.
|
Does it work as expected when running tests from command line or in the CI? The .runsettings file seems to be VS specific. |
I was running it using the .\dotnet.cmd build /t:Test .\src\libraries\System.IO.FileSystem.DriveInfo\tests\System.IO.FileSystem.DriveInfo.Tests.csproj /p:Configuration=Release Which I assume is used by the CI? I am going to run it using a global SDK and get back to you. |
It works both when using |
Ah ok, it is passed to XUnit on command line here:
|
But it is not obvious to me that the extra argument will be passed all the way through for mobile test targets (iOS/Android/browser) that encapsulate the test in an app. I think the existing solution where the test spec is fully encapsulated in the test .dll is better. |
+1. The less msbuild magic that might subtly be missed in various configurations, the better. |
@jkotas @stephentoub Thank you for your feedback. I am going to close the PR and just move |
It's defined in:
runtime/eng/testing/runsettings.targets
Lines 30 to 42 in c66fa99
and I've tested that it works as expected.