ci: fix broken ci, debug and static cases, bump some latest #4954
Conversation
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
Two Ubuntu-based cases (debug build and static build) started failing this past week, unrelated to us. I think the runners change, it seems to be having particular trouble because those tests were trying to use gcc-9. But there's no particular need for that anyway, it just reflects how long ago we last modified those tests. So this spurred a grab bag of CI fixes: * Move the debug and static linkage tests off of raw ubuntu runners and to using the ASWF docker VFX Platform 2025 containers. This makes them more modern and also more stable. * Turns out the "static" test hadn't been working properly lately -- it was accidentally building dynamic libs, not static at all! Fix that, but then it uncovered some problems that are out of scope to fix in this PR. I will look into it separately. In the mean time, I've commented out this test to suppress the failures. * Bump a few of the "latest" dependencies to the most recent. Signed-off-by: Larry Gritz <[email protected]>
lgritz
added
the
build / testing / port / CI
jessey-git
reviewed
Nov 12, 2025
.github/workflows/ci.yml
Outdated
| simd: "avx2,f16c" | ||
| fmt_ver: 11.2.0 | ||
| pybind11_ver: v2.13.6 | ||
| benchmark: 1 |
Contributor
There was a problem hiding this comment.
Just double-checking that benchmark was intended to be enabled here on the Debug config?
Collaborator
Author
There was a problem hiding this comment.
um, no, thanks for catching. I think that's a cut and paste error.
Collaborator
Author
There was a problem hiding this comment.
and I found a couple others I can eliminate
Signed-off-by: Larry Gritz <[email protected]>
jessey-git
approved these changes
Nov 12, 2025
lgritz
merged commit 1417836
into
AcademySoftwareFoundation:main
89 of 95 checks passed
lgritz
added a commit
to lgritz/OpenImageIO
that referenced
this pull request
Nov 13, 2025
…oftwareFoundation#4954) Two Ubuntu-based cases (debug build and static build) started failing this past week, unrelated to us. I think the runners changed yet again, it seems to be having particular trouble because those tests were trying to use gcc-9. But there's no particular need for that anyway, it just reflects how long ago we last modified those tests. So this spurred a grab bag of CI fixes: * Move the debug and static linkage tests off of raw ubuntu runners and to using the ASWF docker VFX Platform 2025 containers. This makes them more modern and also more stable. * Turns out the "static" test hadn't been working properly lately -- it was accidentally building dynamic libs, not static at all! Fix that, but then it uncovered some problems that are out of scope to fix in this PR. I will look into it separately, but in the mean time I have commented out the static build test to suppress the failures. * Bump a few of the "latest" dependencies to the most recent. --------- Signed-off-by: Larry Gritz <[email protected]>
lgritz
added a commit
to lgritz/OpenImageIO
that referenced
this pull request
Nov 13, 2025
…oftwareFoundation#4954) Two Ubuntu-based cases (debug build and static build) started failing this past week, unrelated to us. I think the runners changed yet again, it seems to be having particular trouble because those tests were trying to use gcc-9. But there's no particular need for that anyway, it just reflects how long ago we last modified those tests. So this spurred a grab bag of CI fixes: * Move the debug and static linkage tests off of raw ubuntu runners and to using the ASWF docker VFX Platform 2025 containers. This makes them more modern and also more stable. * Turns out the "static" test hadn't been working properly lately -- it was accidentally building dynamic libs, not static at all! Fix that, but then it uncovered some problems that are out of scope to fix in this PR. I will look into it separately, but in the mean time I have commented out the static build test to suppress the failures. * Bump a few of the "latest" dependencies to the most recent. --------- Signed-off-by: Larry Gritz <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Two Ubuntu-based cases (debug build and static build) started failing this past week, unrelated to us. I think the runners changed yet again, it seems to be having particular trouble because those tests were trying to use gcc-9. But there's no particular need for that anyway, it just reflects how long ago we last modified those tests.
So this spurred a grab bag of CI fixes:
Move the debug and static linkage tests off of raw ubuntu runners and to using the ASWF docker VFX Platform 2025 containers. This makes them more modern and also more stable.
Turns out the "static" test hadn't been working properly lately -- it was accidentally building dynamic libs, not static at all! Fix that, but then it uncovered some problems that are out of scope to fix in this PR. I will look into it separately, but in the mean time I have commented out the static build test to suppress the failures.
Bump a few of the "latest" dependencies to the most recent.