Closed regro-cf-autotick-bot closed 5 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.
@conda-forge/kwant This looks like a weird test error, not related specifically to this rebuild.
Indeed, it's a backwards-incompatble change in pytest; we'll handle it, thanks.
@conda-forge-admin please rerender
Hi! This is the friendly automated conda-forge-webservice.
I tried to re-render for you, but it looks like there was nothing to do.
@conda-forge-admin please rerender
Hi! This is the friendly automated conda-forge-webservice.
I tried to re-render for you, but it looks like there was nothing to do.
If you close and then reopen the PR, the CI services will restart.
@beckermr the pipeline still uses the latest unpinned version of sphinx pytest, contrary to the recipe.
unpinned version of sphinx
Do you mean pytest
?
Try something like pytest =4.6
?
Also this pinning of numpy should be removed, - numpy 1.11
. Just list numpy.
@conda-forge-admin, please rerender
These pinning changes do not require a rerender
The numpy pins matter?! Wow I don't get that.
@akhmerov the tests still fail even though pytest 4.6.4 is installed now.
It is not being installed in the run env. Add the pin there: https://github.com/conda-forge/kwant-feedstock/blob/eb941754c487aef5306d00219c9b99819f798f3e/recipe/meta.yaml#L41
I updated my comment because github links.
The latest error does not seem to be related to pytest
:
Package libgfortran-ng conflicts for:
scipy -> libgcc -> libgfortran-ng[version='>=3.0']
numpy=1.14 -> libgfortran-ng[version='>=3.0']
libcblas==3.8[build=*netlib] -> libblas=3.8.0 -> openblas[version='>=0.3.6,<0.3.7.0a0'] -> libgfortran-ng[version='>=3.0']
mumps-seq -> openblas[version='>=0.3.3,<0.3.4.0a0'] -> libgfortran-ng[version='>=3.0']
Package libgfortran conflicts for:
mumps-seq -> libgfortran[version='>=3.0,<4.0.0.a0|>=3.0.1,<4.0.0.a0']
libcblas==3.8[build=*netlib] -> libgfortran[version='>=3.0.1,<4.0.0.a0|>=4.0.0,<5.0.0.a0']
mumps-seq -> openblas[version='>=0.3.3,<0.3.4.0a0'] -> libgcc -> libgfortran==3.0.1
scipy -> libgfortran[version='>=3.0,<4.0.0.a0|>=3.0.1,<4.0.0.a0|>=4.0.0,<5.0.0.a0']
libblas==3.8[build=*netlib] -> libgfortran[version='>=3.0.1,<4.0.0.a0|>=4.0.0,<5.0.0.a0']
numpy=1.14 -> openblas[version='>=0.2.20,<0.2.21.0a0'] -> libgcc -> libgfortran==3.0.1
libgfortran[version='>=4.0.0,<5.0.0.a0']
libcblas==3.8[build=*netlib] -> libblas=3.8.0 -> openblas[version='>=0.3.6,<0.3.7.0a0'] -> libgcc -> libgfortran==3.0.1
Well now we are getting somewhere!
This rebuild is blocked on this one I think: https://github.com/conda-forge/mumps-feedstock/pull/48
Yay @akhmerov! We are good to merge!
:tada: Thanks for your help @beckermr!
This PR has been triggered in an effort to update to gfortran 7 for OSX.
Notes and instructions for merging this PR:
This package has the following downstream children:
And potentially more. If this PR was opened in error or needs to be updated please add the
bot-rerun
label to this PR. The bot will close this PR and schedule another one.This PR was created by the cf-regro-autotick-bot. The cf-regro-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. If you would like a local version of this bot, you might consider using rever. Rever is a tool for automating software releases and forms the backbone of the bot's conda-forge PRing capability. Rever is both conda (
conda install -c conda-forge rever
) and pip (pip install re-ver
) installable. Finally, feel free to drop us a line if there are any issues!