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.
Parallel check #5819
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Uh oh!
There was an error while loading. Please reload this page.
Parallel check #5819
Changes from 1 commit
ca187078604e57bb6e053b808bf5f414e9901afb59e6efff60473e0fca78cf08570999File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
make eunitsub-targetsWhen called with -jN for N>1, make will run `rebar -r eunit` for all src/* Erlang apps (without the default skipped ones) up to the limit of N times in parallel. This is best used with GNU Make, as it allows for controlling the output of each subtask to be grouped. BSD Make has no such feature and interleaves all parallel target’s output, making it hard to read. For example: gmake -j2 --output-sync=target will run two test suites in parallel and keep their respective outputs separated. It does this by buffering all output before a task is done that means for the first few tests, you don’t see output as you do with serial execution. On my machine I can run up to -j6 relatively stable, making use of all 14 cores. Beyond that, Spurious errors can occur. I’ll file those separately. -j2 shows an almost 2x speed improvement, as expected and things scale relatively linarly up until ~2.5 minutes of runtime, which seems to be a lower bound with all our various setup and wait bits. For comparison, -j1, that is serial execution takes about 10.5 minutes on this machine. Use with care in CI, but definitely use on your local dev machine.Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing