Uh oh!
There was an error while loading. Please reload this page.
Enable parallelism in test projects - #5697
Conversation
…sm on transport tests
johnsimons
commented
Aug 5, 2026
Should we just use the default for |
…orrectly, use default parallelism
rbev
commented
Aug 6, 2026
I removed the explicit setting and it ran much slower, the build agents don't have 4 cores and benefit from having higher parallelism. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
danielmarbach
commented
Aug 6, 2026
Curious did you already compare before and after? How much gain do we get? |
Here's the groupings that have changed, omitting some because they were already parallel from a previous pr, it's based on a single run so take it with a grain of salt.
|
Uh oh!
There was an error while loading. Please reload this page.
This pull request introduces several improvements to the test infrastructure to introduce parallelisation within the test projects to improve CI build times.
Test Infrastructure and Parallelization Enhancements:
FixtureLifeCycle,Parallelizable, andLevelOfParallelism) to bothsrc/Particular.LicensingComponent.UnitTests/NUnitSettings.csandsrc/ServiceControl.AcceptanceTests.RavenDB/NUnitSettings.csto enable test parallelization and control concurrency level.SetupFixtureinsrc/ServiceControl.AcceptanceTests.RavenDB/SetupFixture.csto ensure required event log sources are created before tests run, preventing race conditions during test startup.SemaphoreSlim-based lock andUseDatabaseLifecycleLockmethod inAcceptanceTestStorageConfigurationto serialize database lifecycle operations, preventing parallel access issues with the shared RavenDB server.Test Safety and Reliability:
[NonParallelizable]to avoid race conditions and ensure reliable test execution.Groups with full parallelism
Groups not updated