You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix the docker gate: absolute paths are platform-dependent, and the smoke test counted nine nodes (#10)
`docker-tests` has been red on main since at least 06:46 today, and on every push
before that, on one assertion:
AssertionError: absolute path D:/shots/out was rewritten to
/tmp/ocio_meta_test_xxxx/D:/shots/out
check_output_folder asserts that resolve_output_folder leaves an absolute path
alone, and offers `D:\shots\out` and `\nas\vfx\out` as the examples. What counts
as absolute is os.path.isabs, which answers per platform: both are absolute on
Windows and ordinary relative names on Linux. So in the container the resolver
was asked about a relative path, correctly joined it to the output directory, and
the test called that a failure. The resolver is right; the examples were not
portable. Now each platform is asked about paths it considers absolute, with the
test asserting isabs on its own example first so this cannot rot silently again.
The smoke test that proves the pack imports under ComfyUI listed nine node
classes. There are eleven: OCIOVAEDecode and OCIOVAEEncode were never added, so
if either failed to register the gate would have said "all 9 OCIO nodes
registered" and passed. Added them, and the count in the three messages is now
len(OCIO_NODE_CLASSES) rather than a literal, so the next node does not need a
docs edit to be covered.
Verified: tools/test_write_metadata.py passes on Windows after the change, and
the posix examples are absolute under posixpath while the Windows ones are not,
which is exactly the container's failure.
Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
0 commit comments