-
Notifications
You must be signed in to change notification settings - Fork 164
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
Add AppVeyor jobs for b2 variant=release #46
Merged
Merged
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
This was referenced Mar 16, 2018
mloskot
added a commit
to mloskot/gil
that referenced
this pull request
Mar 18, 2018
This aims to confirm there are no issues depending on build configuration (related to boostorg#46 and 49).
mloskot
added a commit
to mloskot/gil
that referenced
this pull request
Mar 18, 2018
This aims to confirm there are no issues depending on build configuration (related to boostorg#46 and boostorg#49).
mloskot
added a commit
to mloskot/gil
that referenced
this pull request
Mar 28, 2018
This aims to confirm there are no issues depending on build configuration (related to boostorg#46 and boostorg#49).
mloskot
force-pushed
the
ml/add-b2-variant-release
branch
from
March 28, 2018 20:59
7d7bff9
to
86212d3
Compare
@stefanseefeld @chhenning I've cherry-picked the the UB fix commit cead84e into this branch. |
mloskot
added a commit
to mloskot/gil
that referenced
this pull request
Mar 28, 2018
This aims to confirm there are no issues depending on build configuration (related to boostorg#46 and boostorg#49).
mloskot
force-pushed
the
ml/add-b2-variant-release
branch
from
March 28, 2018 21:16
401d69e
to
49e07ae
Compare
3 tasks
I've copied the fix to more places, see #68 |
mloskot
added a commit
to mloskot/gil
that referenced
this pull request
Mar 29, 2018
This aims to confirm there are no issues depending on build configuration (related to boostorg#46 and boostorg#49).
Log CRC that is verified for each test image by test/image.
Patch courtesy of Andrey Semashev via Boost ML.
mloskot
force-pushed
the
ml/add-b2-variant-release
branch
from
March 29, 2018 11:19
49e07ae
to
ee59abd
Compare
Apparently, I have already committed I think, I assumed the I am going to update AppVeyor configuration to bring back |
mloskot
added a commit
to mloskot/gil
that referenced
this pull request
Mar 31, 2018
This aims to confirm there are no issues depending on build configuration (related to boostorg#46 and boostorg#49).
stefanseefeld
pushed a commit
that referenced
this pull request
Jun 27, 2018
Add AppVeyor jobs for b2 variant=release
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.
/cc @chhenning, @stefanseefeld yet another curious case :)
For
variant-debug
all tests pass - this is the default AppVeyor builds variant for current the master.For
variant=release
, run fortest/image.cpp
will likely fail due to mismatch of CRC calculatedbgr121_basic_red_x
image.