conda-forge / aesara-feedstock

A conda-smithy repository for aesara.
BSD 3-Clause "New" or "Revised" License
4 stars 9 forks source link

aesara v2.9.0 #130

Closed regro-cf-autotick-bot closed 1 year ago

regro-cf-autotick-bot commented 1 year ago

It is very likely that the current package version for this feedstock is out of date.

Checklist before merging this PR:

Information about this PR:

  1. Feel free to push to the bot's branch to update this PR if needed.
  2. The bot will almost always only open one PR per version.
  3. The bot will stop issuing PRs if more than 3 version bump PRs generated by the bot are open. If you don't want to package a particular version please close the PR.
  4. If you want these PRs to be merged automatically, make an issue with code>@conda-forge-admin,</codeplease add bot automerge in the title and merge the resulting PR. This command will add our bot automerge feature to your feedstock.
  5. 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. If you do not have permissions to add this label, you can use the phrase code>@<space/conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

Pending Dependency Version Updates

Here is a list of all the pending dependency version updates for this repo. Please double check all dependencies before merging.

Name Upstream Version Current Version
aesara 2.9.0 Anaconda-Server Badge
mkl-service 2.4.0.post1 Anaconda-Server Badge

Dependency Analysis

Please note that this analysis is highly experimental. The aim here is to make maintenance easier by inspecting the package's dependencies. Importantly this analysis does not support optional dependencies, please double check those before making changes. If you do not want hinting of this kind ever please add bot: inspection: false to your conda-forge.yml. If you encounter issues with this feature please ping the bot team conda-forge/bot.

Analysis by source code inspection shows a discrepancy between it and the the package's stated requirements in the meta.yaml.

Packages found by source code inspection but not in the meta.yaml:

Packages found in the meta.yaml but not found by source code inspection:

This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/4928588102, please use this URL for debugging.

conda-forge-webservices[bot] commented 1 year 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.

maresb commented 1 year ago

@conda-forge-admin please rerender

github-actions[bot] commented 1 year ago

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

I tried to rerender for you, but it looks like there was nothing to do.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/aesara-feedstock/actions/runs/4935208166.

maresb commented 1 year ago

Hmm, it's the aarch64 builds which are failing. It seems to be a problem setting up the compilers.

The reported errors are:
- Encountered problems while solving:
-   - package aesara-2.9.0-py310h3e65440_0 requires cxx-compiler, but none of the providers can be installed
-   - package cxx-compiler-1.0.4-h9108069_0 requires gxx_linux-aarch64 7.*, but none of the providers can be installed

It seems to be related to this package specification:

Mamba failed to solve:
 - aesara 2.9.0.* py310h3e65440_0
 - aesara-base 2.9.0.* py310h4c7bcd0_0
 - blas
 - cxx-compiler
 - gcc_linux-aarch64 12.*
 - openblas
 - python >=3.10,<3.11.0a0
 - python_abi 3.10.* *_cp310
 - pip
 - python

I'm not sure yet how to go about solving this.

brandonwillard commented 1 year ago

I'm not sure yet how to go about solving this.

Yeah, good question. Do we have to wait for the other package maintainers to provide/update something?

maresb commented 1 year ago

I really don't know. I'd have to look fairly deeply into it. And even doing that I'm not sure if I'd be successful. Depending on how much we care about aarch64, we could merge it anyway and we just won't get those builds.

Then there's also the new llvm stuff... I'm not sure when that will hit conda-forge, but it seems to be stalled for the moment.

@conda-forge-admin please rerender

brandonwillard commented 1 year ago

I wonder if it's the C compiler version changes (i.e. 11 to 12).

github-actions[bot] commented 1 year ago

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

I tried to rerender for you, but it looks like there was nothing to do.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/aesara-feedstock/actions/runs/4952497820.

maresb commented 1 year ago

Yes!!! Nicely spotted. And it's explicitly in the rerender.

github-actions[bot] commented 1 year 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!

maresb commented 1 year ago

Woah, it worked!!!!

Thanks @brandonwillard!

brandonwillard commented 1 year ago

Looks like we do have to wait for other package maintainers to update things, though.