-
Notifications
You must be signed in to change notification settings - Fork 202
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
Dev pytorch from forge #394
base: dev
Are you sure you want to change the base?
Conversation
Get PyTorch from conda-forge for the CI/CD pipeline.
Remove testing on Win-64 as PyTorch is not available from conda-forge for Win-64 architectures.
In the first round, the conda setup failed (Link to CI/CD) I have no clear idea, why this breaks. Maybe, for every run, a cached environment is updated instead of a new one is created? Or mamba uses cached builds from previous downloads? Maybe, @dominiquesydow or @mbackenkoehler can help? My only guess is to rename the environments in the CI/CD pipeline and in |
Rename environment in CI/CD pipeline to force reinstallation of the full environment instead of using a potentially cached environment
@Old-Shatterhand There is no caching of conda environments or packages. Pasting the error from the raw logs here:
|
Hm, then this run will not succeed as well... |
Description
The current dev branch cannot be published on conda-forge due to PyTorch not being installed from conda-forge but from the pytorch channel. Therefore, I changed the PyTorch installation channel from PyTorch to conda-forge in the CI/CD pipeline to test if the test succeeds with the new dependencies.
Todos
Questions
No questions so far.
Status