ci: switch all containers from aswftesting to aswf #2061
Conversation
aswftesting is no longer maintained. Signed-off-by: Larry Gritz <lg@larrygritz.com>
jfpanisset
left a comment
jfpanisset
left a comment
There was a problem hiding this comment.
That should get you the slimmer images without the baked in Conan download cache.
What's forcing you to remove the bundled OpenImageIO version in the 2024 images and having to rebuild your own with the REMOVE_INSTALLED_OPENIMAGEIO mechanism? I'd be happy to fix that so you don't have to spend CI time rebuilding OIIO.
It's often the case that I want to try combinations of a different OIIO than the one in the container, and sometimes it can be hard to guarantee that cmake only finds one and not any remnants of the others, creating an unholy mixture of headers from one version and libraries from another, or a Python module from one version but a library from another. Especially when one of the installs is in a "system area" that has to get included in various search paths. Sometimes the expedient way to solve this is just to remove the one I don't want from the container. In this particular case, I wanted a newer OIIO for the sanitizer tests. I should really push the sanitizer tests to a more recent container, but I wanted to get this repair out quickly and not spend 3 days fighting some unrelated reason why it might not work in the 2025 or 2026 container. This was just the fastest way to an all-green lineup. |
lgritz
merged commit 3a343a5
into
AcademySoftwareFoundation:main
|
Makes perfect sense, just wanted to make sure there wasn't something specifically broken with the OIIO in the 2024 image which was forcing you to replace it. |
|
No, no flaws in the container as far as I know.
On December 10, 2025 9:55:03 a.m. GMT+09:00, Jean-Francois Panisset ***@***.***> wrote:
jfpanisset left a comment (AcademySoftwareFoundation/OpenShadingLanguage#2061)
Makes perfect sense, just wanted to make sure there wasn't something specifically broken with the OIIO in the 2024 image which was forcing you to replace it.
--
Reply to this email directly or view it on GitHub:
#2061 (comment)
You are receiving this because you are subscribed to this thread.
Message ID: ***@***.***>
--
Larry Gritz
***@***.***
|
…undation#2061) aswftesting is no longer maintained. Signed-off-by: Larry Gritz <lg@larrygritz.com>
3 participants
aswftesting is no longer maintained.