Parallel build all C tests from top level makefile [AP-1086] #1394
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.
Description
@swift-nav/devinfra
A small change to speed up builds of C tests when using the top level makefile, as is done in all CI stages.
The current makefile has 2 sections which build and run tests. They are similar (one targets a subset of tests for compatibility with big endian machines). They are both written as:
Where the first command builds all targets in parallel, and the second runs all the tests sequentially.
However, test targets are not built as part of
all
so what really happens is the mainlibsbp
target is build in parallel in the first step, then all tests are built and run single threaded in the second stage. This can be easily fixed and sped up by altering the first command to build all test targets using the-j4
flag:API compatibility
Does this change introduce a API compatibility risk?
No
API compatibility plan
If the above is "Yes", please detail the compatibility (or migration) plan:
No
JIRA Reference
https://swift-nav.atlassian.net/browse/AP-1086