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
As long as pytorch 1.12 is still used (basically until 1.13.1 comes out), the "mps" backend seems to be too unstable to use it, failing several of the tests. Even setting PYTORCH_ENABLE_MPS_FALLBACK=1 in the environment does not fully remove this issue.
馃敩 How To Reproduce
Steps to reproduce the behavior:
run make fast-test (or any other command) on macOS with "mps" support
Environment
OS: macOS
Python version: 3.9.7
馃搱 Expected behavior
Tests should run successfully
馃搸 Additional context
A quickfix would be to set the default device in inseq.utils.torch_utils.py to "cpu" for mps-environments as well for now, until pytorch 1.13.1 is released.
馃悰 Bug Report
As long as pytorch 1.12 is still used (basically until 1.13.1 comes out), the "mps" backend seems to be too unstable to use it, failing several of the tests. Even setting
PYTORCH_ENABLE_MPS_FALLBACK=1
in the environment does not fully remove this issue.馃敩 How To Reproduce
Steps to reproduce the behavior:
make fast-test
(or any other command) on macOS with "mps" supportEnvironment
馃搱 Expected behavior
Tests should run successfully
馃搸 Additional context
A quickfix would be to set the default device in
inseq.utils.torch_utils.py
to "cpu" for mps-environments as well for now, until pytorch 1.13.1 is released.The text was updated successfully, but these errors were encountered: