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
All of pytorch_version: 2.3.1, pytorch_version: 2.3.1+cpu, or pytorch_version: 2.3.1+cu121 will make installation of PyTorch fail, which is fixed by Fynn already.
I think it complicates things if PyTorch version 2.3.1 is converted to 2.3.1+cu121 automatically by packaging when CI doesn't make use of GiHub Actions' GPU feature. Either of these should change.
Do the tests fail with those versions running in CI?
Have you tried adding the cpuonly package to the dependencies? (see https://pytorch.org/get-started/locally/)
The memories are vague. Maybe it doesn't cause failed tests. But I was saying for CIs the code should either use GPU packages on GPU-enabled CI machines, or use CPU-only packages on traditional CI machines.
for model uploads that do specify a conda environment that may not be the case, but I'd rather not mess with those environments contributed by users as long as the CI passes.
closing for now. We'll visit this topic again when also running CI with GPUs eventually...
pytorch_version: 2.3.1
,pytorch_version: 2.3.1+cpu
, orpytorch_version: 2.3.1+cu121
will make installation of PyTorch fail, which is fixed by Fynn already.2.3.1
is converted to2.3.1+cu121
automatically by packaging when CI doesn't make use of GiHub Actions' GPU feature. Either of these should change.The text was updated successfully, but these errors were encountered: