search

conda-forge / netcdf4-feedstock

A conda-smithy repository for netcdf4.
BSD 3-Clause "New" or "Revised" License
3 stars 25 forks source link

MNT: rerender #101

Closed conda-forge-linter closed 4 years ago

conda-forge-linter commented 4 years ago

Hi! This is the friendly automated conda-forge-webservice.

I've rerendered the recipe as instructed in #100.

Here's a checklist to do before merging.

conda-forge-linter commented 4 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.

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

For recipe:

github-actions[bot] commented 4 years ago

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

Thus the PR was passing and merged! Have a great day!

ocefpaf commented 4 years ago

Looks like we can reproduce #101 on the CIs. @xhochy could this be related to the libssh2 change?

isuruf commented 4 years ago

Can you check which dependencies changed from the last successful run?

ocefpaf commented 4 years ago

Can you check which dependencies changed from the last successful run?

> diff passing.txt failing.txt 
4c4
< cftime:          1.1.1.2-py38h4b8e87e_0    conda-forge
---
> cftime:          1.1.3-py38h40bdaab_0      conda-forge
9c9
< intel-openmp:    2020.0-166                defaults   
---
> intel-openmp:    2020.1-216                defaults   
16,17c16,17
< libnetcdf:       4.7.4-nompi_h256d12c_103  conda-forge
< libssh2:         1.8.2-h642c060_2          conda-forge
---
> libnetcdf:       4.7.4-nompi_h256d12c_104  conda-forge
> libssh2:         1.9.0-h3235a2c_1          conda-forge
24c24
< setuptools:      46.1.3-py38h32f6830_0     conda-forge
---
> setuptools:      46.3.1-py38h32f6830_0     conda-forge
dopplershift commented 4 years ago

Is it really necessary to pin to mkl/intel-openmp? By locking to 2020, this became package incompatible with the only windows build of scipy 1.5.0. I'm not saying I have to have netcdf4-1.5.4, but I just lost over an hour trying to figure out why an environment I was trying to set up had conflicts. Needless to say, netcdf4 + scipy as conflicting was not an early guess.

isuruf commented 4 years ago

Don't know. Can you send a PR to loosen it?

dopplershift commented 4 years ago

Trying in #104 .