[WIP] ci: parallelise the running of gopherjs tests #796
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
0606312 to
6ac1f4a
Compare
6ac1f4a to
20a0780
Compare
Currently we run the gopherjs tests in sequence; this is limited to a single CPU core because we ultimately run the tests via Node. We can improve on this by concurrently running gopherjs test per package. Also implemented a fix discussed in a previous issue/PR to make our list of package exclusions explicit, via std_test_pkg_exclusions
20a0780 to
4dd3bfa
Compare
|
I'm going to abandon this change because I'm losing too much time to fighting CircleCI! For anyone who wants to parallelise local tests: will use all your cores to run the |
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.
DO NOT REVIEW
DO NOT MERGE
Based on #797 - this will need a rebase once #797 is merged.
See the diff this PR introduces on top of #797 here
Currently we run the gopherjs tests in sequence; this is limited to a
single CPU core because we ultimately run the tests via Node. We can
improve on this by concurrently running gopherjs test per package.
myitcv.io/cmd/concsh helps do does just that:
https://github.com/myitcv/x/blob/master/cmd/concsh/README.md
Also implemented a fix discussed in a previous issue/PR to make our list
of package exclusions explicit, via std_test_pkg_exclusions