-
-
Notifications
You must be signed in to change notification settings - Fork 4
Enable tests by adding separate torchcodec-tests output [Debugging] #5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@conda-forge-admin, please rerender |
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipe/recipe.yaml:
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/14647613176. Examine the logs at this URL for more detail. |
…nda-forge-pinning 2025.04.23.13.34.55
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
@conda-forge-admin please rerender |
…nda-forge-pinning 2025.04.23.13.34.55
This PR requires conda-forge/admin-requests#1501 to be merged for the CI to be green. |
Test on linux-aarch64 are failing (just the top of the output, the failure are much longer):
|
I am not sure if the failure is due to the emulation or due to linux-aarch64, I probably need to check on a physical linux-aarch64 machine. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR updates the CI configurations to enable tests with a separate torchcodec-tests output and removes redundant version pinning for libtorch and pytorch by aligning them with the global pin (set to 2.6). Key changes include:
- Adding "libtorch" pin entries with version '2.6' across multiple YAML config files.
- Adding "pytorch" pin entries with version '2.6' across the same configuration files.
- Updating the Azure Pipelines matrix to reference the new cuda_compiler-based configuration names.
Reviewed Changes
Copilot reviewed 34 out of 34 changed files in this pull request and generated no comments.
Show a summary per file
File | Description |
---|---|
.ci_support/linux_aarch64_cuda_compiler_versionNonepython3.13.____cp313.yaml | Added libtorch and pytorch version pins |
.ci_support/linux_aarch64_cuda_compiler_versionNonepython3.12.____cpython.yaml | Added libtorch and pytorch version pins |
.ci_support/linux_aarch64_cuda_compiler_versionNonepython3.11.____cpython.yaml | Added libtorch and pytorch version pins |
.ci_support/linux_aarch64_cuda_compiler_versionNonepython3.10.____cpython.yaml | Added libtorch and pytorch version pins |
.ci_support/linux_aarch64_cuda_compiler_version12.6python3.9.____cpython.yaml | Added libtorch and pytorch version pins |
.ci_support/linux_aarch64_cuda_compiler_version12.6python3.13.____cp313.yaml | Added libtorch and pytorch version pins |
.ci_support/linux_aarch64_cuda_compiler_version12.6python3.12.____cpython.yaml | Added libtorch and pytorch version pins |
.ci_support/linux_aarch64_cuda_compiler_version12.6python3.11.____cpython.yaml | Added libtorch and pytorch version pins |
.ci_support/linux_aarch64_cuda_compiler_version12.6python3.10.____cpython.yaml | Added libtorch and pytorch version pins |
.ci_support/linux_64_cuda_compiler_versionNonepython3.9.____cpython.yaml | Added libtorch and pytorch version pins |
.ci_support/linux_64_cuda_compiler_versionNonepython3.13.____cp313.yaml | Added libtorch and pytorch version pins |
.ci_support/linux_64_cuda_compiler_versionNonepython3.12.____cpython.yaml | Added libtorch and pytorch version pins |
.ci_support/linux_64_cuda_compiler_versionNonepython3.11.____cpython.yaml | Added libtorch and pytorch version pins |
.ci_support/linux_64_cuda_compiler_versionNonepython3.10.____cpython.yaml | Added libtorch and pytorch version pins |
.ci_support/linux_64_cuda_compiler_version12.6python3.9.____cpython.yaml | Added libtorch and pytorch version pins |
.ci_support/linux_64_cuda_compiler_version12.6python3.13.____cp313.yaml | Added libtorch and pytorch version pins |
.ci_support/linux_64_cuda_compiler_version12.6python3.12.____cpython.yaml | Added libtorch and pytorch version pins |
.ci_support/linux_64_cuda_compiler_version12.6python3.11.____cpython.yaml | Added libtorch and pytorch version pins |
.ci_support/linux_64_cuda_compiler_version12.6python3.10.____cpython.yaml | Added libtorch and pytorch version pins |
.azure-pipelines/azure-pipelines-linux.yml | Updated matrix configuration keys to reference the new cuda_compiler-based configurations |
As the |
Actually an attempt we can do is to try emulated builds instead of cross-compilation. |
@conda-forge-admin please rerender |
…nda-forge-pinning 2025.04.25.09.56.22
@conda-forge-admin please rerender |
…nda-forge-pinning 2025.04.25.09.56.22
The test failures are there also switching from cross-compilation to emulation, so they are probably not related to cross-compilation. They may be related to the emulation of tests, we should try to run them without emulation, and see if they fail also there. The same failures are there also on 0.3.0, see: #6 . |
In 305374a I switched back to cross-compilation. |
@conda-forge-admin please rerender |
…nda-forge-pinning 2025.04.25.23.47.09
As this PR turned out to be more a debugging sandbox, I opened #7 for the PR for actually adding tests. |
Hi! This is the friendly automated conda-forge-linting service. I was trying to look for recipes to lint for you, but it appears we have a merge conflict. Please try to merge or rebase with the base branch to resolve this conflict. Please ping the 'conda-forge/core' team (using the |
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
The test failures have been reproduced in https://github.com/traversaro/torchcodec-test-debug and reported in pytorch/torchcodec#569 (comment), so we can close this. |
As discussed in conda-forge/staged-recipes#29447 (comment) . The structure of using a separate (empty)
torchcodec-tests
output that only contains the (heavyweight) files used for tests is inspired from the torchvision-feedstock.I also removed the manual pin of libtorch and pytorch to 2.6.* as now the global pinning are using 2.6, see conda-forge/conda-forge-pinning-feedstock#7208 .
Checklist
0
(if the version changed)conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)