Added CI framework #185
Closed
Added CI framework #185
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
- travis with valgrind, cppcheck, ubsan, codecov, covscan (future) - appveyor with MSVC 2010 through 2017, cygwin 32/64, mingw 32/64 - README, LICENSE, etc. - Fixed example Jamfile to build examples based on C++ features This fixes boostorg#146
Codecov Report
@@ Coverage Diff @@
## develop #185 +/- ##
==========================================
Coverage ? 46.72%
==========================================
Files ? 92
Lines ? 5203
Branches ? 2279
==========================================
Hits ? 2431
Misses ? 1112
Partials ? 1660Continue to review full report at Codecov.
|
|
#177 can be seen in the build failures for clang here. |
Closed
|
In branch |
|
In master. Thanks! |
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.
Please see my fork's PR for build results.
jeking3#1
A number of builds are failing for various reasons - mostly clang due to release optimizer issues in doc_example22 and doc_example23 that needs to be resolved.
As we also discussed by email, the static and UBSAN analyses may need additional work to annotate the intentional issues (this repository is unique, as we're testing a test library). I can update this PR to mark those as expected failures once we resolve the others.