ci: fix using fmt master with OIIO main build#2095
Merged
lgritz merged 1 commit intoAcademySoftwareFoundation:mainfrom Mar 20, 2026
Merged
ci: fix using fmt master with OIIO main build#2095lgritz merged 1 commit intoAcademySoftwareFoundation:mainfrom
lgritz merged 1 commit intoAcademySoftwareFoundation:mainfrom
Conversation
A recent change in OIIO main is to check that any auto-built dependencies have a SHA-1 hash that matches what we think it should be for that version. That works fine for a fixed version, but if we are asking for OIIO to build from dependency master/main, as we do from its "bleeding edge" CI variant, we need to tell it that it's ok to not match the expected hash by setting OpenImageIO_DEPENDENCY_BUILD_ALLOW_UNVERIFIED_TAGS=ON. So we need to do this in the OSL bleeding edge variant, too. Signed-off-by: Larry Gritz <lg@larrygritz.com>
Collaborator
Author
|
Merging without review because it fixes broken CI, but doesn't change any code. |
lgritz
added a commit
to lgritz/OpenShadingLanguage
that referenced
this pull request
Mar 20, 2026
…ion#2095) A recent change in OIIO main is to check that any auto-built dependencies have a SHA-1 hash that matches what we think it should be for that version. That works fine for a fixed version, but if we are asking for OIIO to build from dependency master/main, as we do from its "bleeding edge" CI variant, we need to tell it that it's ok to not match the expected hash by setting OpenImageIO_DEPENDENCY_BUILD_ALLOW_UNVERIFIED_TAGS=ON. So we need to do this in the OSL bleeding edge variant, too. Signed-off-by: Larry Gritz <lg@larrygritz.com>
lgritz
added a commit
to lgritz/OpenShadingLanguage
that referenced
this pull request
Mar 20, 2026
…ion#2095) A recent change in OIIO main is to check that any auto-built dependencies have a SHA-1 hash that matches what we think it should be for that version. That works fine for a fixed version, but if we are asking for OIIO to build from dependency master/main, as we do from its "bleeding edge" CI variant, we need to tell it that it's ok to not match the expected hash by setting OpenImageIO_DEPENDENCY_BUILD_ALLOW_UNVERIFIED_TAGS=ON. So we need to do this in the OSL bleeding edge variant, too. Signed-off-by: Larry Gritz <lg@larrygritz.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
A recent change in OIIO main is to check that any auto-built dependencies have a SHA-1 hash that matches what we think it should be for that version. That works fine for a fixed version, but if we are asking for OIIO to build from dependency master/main, as we do from its "bleeding edge" CI variant, we need to tell it that it's ok to not match the expected hash by setting
OpenImageIO_DEPENDENCY_BUILD_ALLOW_UNVERIFIED_TAGS=ON. So we need to do this in the OSL bleeding edge variant, too.