search

conda-forge / vtk-feedstock

A conda-smithy repository for vtk.
BSD 3-Clause "New" or "Revised" License
13 stars 64 forks source link

MNT: Re-render the feedstock #26

Closed conda-forge-admin closed 7 years ago

conda-forge-admin commented 7 years ago

Hi! This is the friendly conda-forge-admin automated user.

I've re-rendered this feedstock with the latest version of conda-smithy (2.2.1) and noticed some changes. If the changes look good, then please go ahead and merge this PR. If you have any questions about the changes though, please feel free to ping the 'conda-forge/core' team (using the @ notation in a comment).

Remember, for any changes to the recipe you would normally need to increment the version or the build number of the package. Since this is an infrastructural change, we don't actually need/want a new version to be uploaded to anaconda.org/conda-forge, so the version and build/number are left unchanged and the CI has been skipped.

Thanks!

conda-forge-linter commented 7 years ago

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.

patricksnape commented 7 years ago

So the issue here seems to be that we now time out if we add Python 3.6

Korijn commented 7 years ago

We already disabled a bunch of configurations due to the timeouts, so adding a new one would push the build over the boundary again, yes. I do think 3.6 is more important than e.g. 3.4, so maybe you can work with that...

patricksnape commented 7 years ago

Python 3.4 is already removed as far as I can tell?

Korijn commented 7 years ago

That's problematic then... :)

Korijn commented 7 years ago

I remember there was some word about manually uploading specific builds? Might be a lot more resource-effective for ContinuumIO to free up some cash to increase your CI build timeout limits though...