Closed bittremieux closed 4 months ago
It does seem like we're immediately running into MPS-related errors. @wfondrie is this something you can easily diagnose?
I tried to set PYTPYTORCH_MPS_HIGH_WATERMARK_RATIO=0.0
, as suggested by the error message, but that didn't solve the issue. There are (conflicting) reports here that this issue might get solved in PyTorch 2.3, which is scheduled for release in April.
As a non-macOS user and lacking familiarity with this error, I currently don't see many other options than to wait until then.
Apparently MPS is not actually available for the GitHub Action runners, so there's no way to test this currently. #327 has disabled running on M1/M2 chips (which will automatically try to use MPS), so at least our tests don't fail anymore.
See here for the available (free) runners for GitHub Actions.