v1.8 -> v1.9

[benjaminrwilson]

Checklist

• Used a personal fork of the feedstock to propose changes
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.

Here's what I've got...

For recipe:

• The outputs section contained an unexpected subsection name. activate_in_script is not a valid subsection name.

For recipe:

• It looks like the 'pytorch-cpu' output doesn't have any tests.

[izahn]

@conda-forge-admin please rerender

[benjaminrwilson]

@isuruf, it appears that some of the Windows builds are immediately failing. Do you think we can just skip these?

[benjaminrwilson]

@hmaarrfk, would you mind taking a look at this when you get a chance as well?

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I was trying to look for recipes to lint for you, but it appears we have a merge conflict.
Please try to merge or rebase with the base branch to resolve this conflict.

Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug.

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.

Here's what I've got...

For recipe:

• The outputs section contained an unexpected subsection name. activate_in_script is not a valid subsection name.

For recipe:

• It looks like the 'pytorch-cpu' output doesn't have any tests.

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.

Here's what I've got...

For recipe:

• The outputs section contained an unexpected subsection name. activate_in_script is not a valid subsection name.

[conda-forge-linter]

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 (recipe) and found it was in an excellent condition.

[benjaminrwilson]

@conda-forge/core, what is the best practice here for circumventing the Azure CI timeout? Is the only option to build locally?

[hmaarrfk]

Currently yes. We have been buliding these packages manually on personally hardware. Rather tedious but dooable for linux.

Did you get the recipe updated? Seems like things are passing. Encouraging!

[benjaminrwilson]

Ah, I see. Yes, the recipe is updated and seems to be working. I wonder if we could limit gpu architectures that this is being built against to try and get within the timeout limit.

[benjaminrwilson]

@hmaarrfk and @isuruf, who previously built these locally? Do you think they'd be willing to help us out?

[hmaarrfk]

I wonder if we should wait for the MKL migration as well. I think the bot is going to be doing an other round and starting a build soon. Do you want me to test building a CUDA build?

[benjaminrwilson]

@hmaarrfk, a CUDA build would be much appreciated! I wonder if there's a way to split up the compute architecture builds into separate jobs (to try to avoid the CI timeout)?

[hmaarrfk]

I might not have time to start one until Sunday Afternoon. For what its worth, you should be able to test local hardware with python build-locally.py

[hmaarrfk]

My machiens are just currently in use.

[hmaarrfk]

I'm kinda happy with this as is now.

A GPU build
https://anaconda.org/ramonaoptics/pytorch-gpu
https://anaconda.org/ramonaoptics/pytorch

Was successful.

@isuruf do we want to build them all here before merging?

[hmaarrfk]

@isuruf thank you for the review. I started a build tracker.

For those that want to help chose a build, and run the command:

python build-locally.py CONFIG_IN_THE_TABLE

and fill in the table with your name and start time (just so that we can get a feeling of the expected end date).

I started 4 at time on a largeish machine i have. I hope that the machine can handle it.

[hmaarrfk]

nvm, on my computer, the disk is full..... managing the space taken by docker is no fun....

[isuruf]

Please wait until the review is over and this Pr is merged

[hmaarrfk]

ok, will do.

[conda-forge-linter]

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 (recipe) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe:

• It looks like the 'pytorch-cpu' output doesn't have any tests.

[benjaminrwilson]

@hmaarrfk and @isuruf, thanks for the reviews. Let me know if you have any other concerns.

[isuruf]

@conda-forge-admin, rerender