Use -fsyntax-only in Jenkins #1350
Open
Conversation
This file contains 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
2 tasks
WardBrian
force-pushed
the
ci/syntax-only
branch
2 times, most recently
from
5586de1
to
7a23f46
Compare
WardBrian
force-pushed
the
ci/syntax-only
branch
from
f1227e5
to
b57c366
Compare
|
This shaves ~20-30 minutes off of the CI compared to what we do right now. If we don't actually care about code-generating or linking of the stanc-generated code, it seems like a nice speedup |
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.
Submission Checklist
Release notes
Try to use
-fsyntax-onlyargument to Clang to speed up CI during the phases that only check if something actually compiles.Copyright and Licensing
By submitting this pull request, the copyright holder is agreeing to
license the submitted work under the BSD 3-clause license (https://opensource.org/licenses/BSD-3-Clause)