torchcodec-xpu: update dependencies to torchcodec 0.13.0#56
Merged
Conversation
Contributor
Author
|
CI fails with: This means that upstream pytorch migrated to oneAPI 2026.0. We need to update: torchlib-xpu/.github/workflows/ci.yml Line 109 in b97df4e |
Contributor
Author
Fixed in: |
Fixes: intel#55 Signed-off-by: Dmitry Rogozhkin <dmitry.v.rogozhkin@intel.com>
PyTorch XPU builds of the same major version series (2.x) might be done with different major versions of oneAPI toolchain which makes them incompatible with each other. For example, torch 2.12 is built with 2025.3.x and 2.13 with 2026.0. This means that we can't set dependency from torch as >=2.12. The best we can do is to pin dependency to specific torch version, i.e. `torch~=2.12.0`. Torchcodec is not yet stable enough to guarantee forward compatibility. Besides that we reuse torchcodec test system with some patching. This trick requires alignment between torchcodec we install for validation and torchcodec we use for testing. Thus, we also need to pin specific torchcodec version, i.e. `torchcodec~=0.13.0`. Signed-off-by: Dmitry Rogozhkin <dmitry.v.rogozhkin@intel.com>
dvrogozh
changed the title
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
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.
PyTorch XPU builds of the same major version series (2.x) might be done with different major versions of oneAPI toolchain which makes them incompatible with each other. For example, torch 2.12 is built with 2025.3.x and 2.13 with 2026.0. This means that we can't set dependency from torch as >=2.12. The best we can do is to pin dependency to specific torch version, i.e.
torch~=2.12.0.Torchcodec is not yet stable enough to guarantee forward compatibility. Besides that we reuse torchcodec test system with some patching. This trick requires alignment between torchcodec we install for validation and torchcodec we use for testing. Thus, we also need to pin specific torchcodec version, i.e.
torchcodec~=0.13.0.