-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
pytorch 2.1.2 #216
pytorch 2.1.2 #216
Conversation
Signed-off-by: Julien Jerphanion <[email protected]>
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( I do have some suggestions for making it better though... For recipe:
|
@conda-forge-admin, please rerender |
Hi! This is the friendly automated conda-forge-webservice. I tried to rerender for you but ran into some issues. Please check the output logs of the latest rerendering GitHub actions workflow run for errors. You can also ping conda-forge/core for further assistance or try re-rendering locally. This message was generated by GitHub actions workflow run https://github.com/conda-forge/pytorch-cpu-feedstock/actions/runs/7660230636. |
Signed-off-by: Julien Jerphanion <[email protected]>
…nda-forge-pinning 2024.01.26.15.16.22
@jaimergp: could you repush an empty commit, please? |
Thank you, @jaimergp. It seems that one workflow is marked as failed, but it is not possible to access its logs. Should we rerun all of them? |
I've rerun failures once. I think we are close to resource exhaustion and some workers die. Let's give it a 2nd try. |
I think there is a warning which is duplicated multiple times and which spams the logs showing the job as failing even-though the job itself might not fail. |
Yeah, @hmaarrfk has been building that job manually. |
OK, then is this PR ready for reviews? |
Yes |
@@ -53,7 +53,7 @@ python: | |||
- 3.8.* *_cpython | |||
- 3.9.* *_cpython | |||
pytorch: | |||
- '2.0' | |||
- '2.1' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might the previous builds for 2.1.0
be compromised?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this pin is somewhat ignored. This funny thing is happening in rendering this repo that is odd with the PyTorch pinning
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I find the behaviour of conda build misleading.
log files for cuda112 + linux: |
Thank you, @hmaarrfk. |
Checklist
0
(if the version changed)conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)