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.
this is something I always wanted - a test runner just runs Julia's own
Test
but in parallel and only based on file names without asking people puttinginclude
inside@testset
, e.gthis seems to be a quite common pattern in the ecosystem, and at least causing me to keep forgetting to include newly added tests quite often.
ion test
basically just treats any dir/file starting withtest_
as a separate test job and runs that with the following scriptthen collect the test report in async fashion (so we can make use of multi-threading) and print failed tests in the end, with
-v, --verbose
print the full test report optionally.async schedule via tokiouse rayon for a work-stealing schedule fits our needs of nested parallelism better--test-threads
option