Use XUnit.jl for parallel testing. #121
Merged
Conversation
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
Member
Author
maleadt
force-pushed
the
tb/xunit
branch
2 times, most recently
from
61efb4f to
e1f8376
Compare
Member
Author
|
CI failure is RelationalAI-oss/XUnit.jl#19. Let's wait until RelationalAI-oss/XUnit.jl#21 is merged and tagged. |
Member
Author
|
I'm impatient, let's go with the hack for now. |
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.
Another attempt... I'm not sure why I reverted the previous one, presumably because it was using multiple threads, which doesn't really accelerate the test suite because we're doing lots of compilation here (which is still single-threaded)?
In any case, with the distributed test runner I can run the entire GemmKernels.jl test suite in 3 minutes or so.