-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Merged PR #925 breaks CPU-Only installs #931
Comments
I can confirm this issue. |
I am facing the same issue as well but in my case I am facing the issue when trying to install apex in a GPU machine. Was anyone able to fix it ? |
same here |
@raghava14 The fix that we were able to make was install Apex using the commit before the one that broke the installation. Obviously this is not good in the long run but its a fine temporary fix |
Thanks for reporting this issue. The |
Please do not consider the fix an endorsement of Apex as a future-proof source of mixed precision. torch.cuda.amp is the truth. It's much easier to use. The modularity and flexibility makes it almost fun. |
Even if torch.cuda.amp must be the ground truth :) if we need fusedadam, Apex is still required, and can confirm #937 does not fix the issue. Needs to be reopen. |
Run this command |
While running a Github CD job, it attempted to install Apex, but failed with the following traceback:
It seems that cuda_dir is None, which is intuitively expected when installing Apex on a CPU only machine. But even when installing on a CPU only machine, the setup is still looking for the Nvidia Cross-Compilers.
The most recent commit as of 8/4/2020 (hash: 5b53121...) adds this line into setup, which breaks the install.
The corresponding line within the current release of Apex:
apex/setup.py
Line 14 in 5b53121
The text was updated successfully, but these errors were encountered: