Parallelise unit tests with ParallelTestRunner - #499
Merged
Conversation
htsnowden
approved these changes
Aug 11, 2026
htsnowden
left a comment
Collaborator
There was a problem hiding this comment.
This looks good to me. Should there be something added to the developer docs page to cover how to do tests
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Instead of splitting unit tests into groups based on the ordering in
runtests.jl, have multiple parallel workers execute every separate test file instead. This reduces setup overhead and hopefully should make things slightly faster.Strategy for future unit tests.
test/Project.toml, not the mainProject.toml.include()statements in test sets.test/will be read automatically, no need to add anything more totest/runtests.jl.