Make the 'bleeding edge' CI test build libtiff and openexr from master #2543
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
The idea of this "bleeding edge" entry in the CI test matrix is to really use the very latest toolchain, in order to spot problems long before users will encounter them. To that end, let's make sure we are building and testing the current master of libtiff and OpenEXR.
|
Not that I'm suggesting you actually go to the trouble to do this, but if you moved over to Fedora Rawhide you would also get the latest GCC. Rawhide is basically the test ground for gcc pre-releases. |
|
GitHub CI doesn't give me the option to switch to a different distro. |
|
Yeah, that's a shame too. I think there's a way to do it through docker but that's probably more trouble than it's worth. |
lgritz
added a commit
to lgritz/OpenImageIO
that referenced
this pull request
Apr 11, 2020
AcademySoftwareFoundation#2543) The idea of this "bleeding edge" entry in the CI test matrix is to really use the very latest toolchain, in order to spot problems long before users will encounter them. To that end, let's make sure we are building and testing the current master of libtiff and OpenEXR.
lgritz
added a commit
to lgritz/OpenImageIO
that referenced
this pull request
Apr 22, 2020
AcademySoftwareFoundation#2543) The idea of this "bleeding edge" entry in the CI test matrix is to really use the very latest toolchain, in order to spot problems long before users will encounter them. To that end, let's make sure we are building and testing the current master of libtiff and OpenEXR.
lgritz
added a commit
to lgritz/OpenImageIO
that referenced
this pull request
Apr 22, 2020
AcademySoftwareFoundation#2543) The idea of this "bleeding edge" entry in the CI test matrix is to really use the very latest toolchain, in order to spot problems long before users will encounter them. To that end, let's make sure we are building and testing the current master of libtiff and OpenEXR.
lgritz
added a commit
to lgritz/OpenImageIO
that referenced
this pull request
Apr 23, 2020
AcademySoftwareFoundation#2543) The idea of this "bleeding edge" entry in the CI test matrix is to really use the very latest toolchain, in order to spot problems long before users will encounter them. To that end, let's make sure we are building and testing the current master of libtiff and OpenEXR.
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.
The idea of this "bleeding edge" entry in the CI test matrix is to
really use the very latest toolchain, in order to spot problems long
before users will encounter them.
To that end, let's make sure we are building and testing the current
master of libtiff and OpenEXR.