fix: Use more modern span-based set_pixels with OIIO 3.1. #2042
Conversation
Switch CI back to the aswf/ci-osl:2025-clang18.3 container that has OIIO 3.1, it will work fine with this change. Signed-off-by: Larry Gritz <[email protected]>
|
@jfpanisset This is the fix that makes the OptiX tests work with OIIO 3.1, it was my fault after all and your bumping the container helped me identify an important bug. (To be pendantic, this change is not the fix, this is an OSL-wide workaround that avoids the OIIO bug by using a newer, and working, version of the call, which we should have switched to anyway as it is the preferred one, regardless. The actual bug fix on the OIIO side is AcademySoftwareFoundation/OpenImageIO#4949) |
|
Seems reasonable. If the GPU CI is going to be testing "bleeding edge", do you want to use the 2026 container? There shouldn't be much difference for OSL since even the 2025 container is using OIIO 3.1.x anyway. |
|
I think when the 2026 container is updated, I'll maybe set up a second OptiX job -- one on 2025 using 2025 era releases, and one using 2026 closer to bleeding edge. |
2 participants
Switch CI back to the aswf/ci-osl:2025-clang18.3 container that has OIIO 3.1, it will work fine with this change.