-
Notifications
You must be signed in to change notification settings - Fork 724
Revise Linux CPU unittests CI workflow #4098
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
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/audio/4098
Note: Links to docs will display an error until the docs builds have been completed. ⏳ 6 Pending, 7 Unrelated FailuresAs of commit 84d2a99 with merge base f0a4999 ( FLAKY - The following job failed but was likely due to flakiness present on trunk:
BROKEN TRUNK - The following jobs failed but was present on the merge base:👉 Rebase onto the `viable/strict` branch to avoid these failures
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
065de1f
to
603c3e7
Compare
3cb6bb4
to
95c8d2d
Compare
Strange- why isn't CI running any more? Perhaps the force pushing confused github. I had to trigger it manually. The run is at https://github.com/pytorch/audio/actions/runs/17588954128 |
51947f0
to
268ee86
Compare
I'm getting the deadly "Could not load libtorchcodec" error from an incorrectly installed ffmpeg. But conda should be installing ffmpeg correctly! Very confusing. |
b77abdf
to
9f01734
Compare
I saw this as well. Adding
fixed that. |
b648cdf
to
84d2a99
Compare
As we've decided against the approach to solving the CI ffmpeg>4 incompatibility issue by installing our own miniconda and ignoring the pytorch-infra environment (begun in #4093), this draft PR tries a different approach: using a standard github runner, as is used to build the docs for torchcodec.
Note that this PR depends on files included in #4095 , so it has that PR as a target.