Closed regro-cf-autotick-bot closed 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.
Drone CI failures are weird. Apparently we can't run import numba
? llvmlite
packages are the same as when they passed in PR ( https://github.com/conda-forge/numba-feedstock/pull/56 ) before (ignoring some unrelated Windows Python 3.8 changes). Am I missing something?
import: 'numba'
3133 Traceback (most recent call last):
3134 File "/drone/src/build_artifacts/numba_1598558181813/test_tmp/run_test.py", line 2, in <module>
3135 import numba
3136 File "/drone/src/build_artifacts/numba_1598558181813/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeh/lib/python3.6/site-packages/numba/__init__.py", line 14, in <module>
3137 from numba.core import config
3138 File "/drone/src/build_artifacts/numba_1598558181813/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeh/lib/python3.6/site-packages/numba/core/config.py", line 16, in <module>
3139 import llvmlite.binding as ll
3140 File "/drone/src/build_artifacts/numba_1598558181813/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeh/lib/python3.6/site-packages/llvmlite/binding/__init__.py", line 4, in <module>
3141 from .dylib import *
3142 File "/drone/src/build_artifacts/numba_1598558181813/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeh/lib/python3.6/site-packages/llvmlite/binding/dylib.py", line 3, in <module>
3143 from llvmlite.binding import ffi
3144 File "/drone/src/build_artifacts/numba_1598558181813/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeh/lib/python3.6/site-packages/llvmlite/binding/ffi.py", line 153, in <module>
3145 raise OSError("Could not load shared object file: {}".format(_lib_name))
3146 OSError: Could not load shared object file: libllvmlite.so
3147 Tests failed for numba-0.51.1-py36h7c3b610_0.tar.bz2 - moving package to /drone/src/build_artifacts/broken
cc @stuartarchibald (in case you have thoughts)
Looks like there was a rebuild of libllvm10
recently ( https://github.com/conda-forge/llvmdev-feedstock/pull/98 ). Going to try rebuilding llvmlite
( https://github.com/conda-forge/llvmlite-feedstock/pull/46 ) and see if that helps.
@jakirkham would guess at linkage, missing symbol?
Yeah that seems like a reasonable hypothesis. Though the only thing libllvm10
changed is run_exports
( https://github.com/conda-forge/llvmdev-feedstock/pull/98 ) (as opposed to some build related change), which I wouldn't have expected to cause this kind of issue.
It looks like the new llvmlite
builds on aarch64
are segfaulting during testing ( https://github.com/conda-forge/llvmlite-feedstock/pull/46#issuecomment-682181503 ).
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!
@conda-forge-admin, please restart CI.
Looks like PR ( https://github.com/conda-forge/llvmdev-feedstock/pull/99 ) and rebuild of llvmlite
with the more relaxed libllvm10
pinning fixed it. Thanks for the help everyone 😀
Thanks.
Thanks for sorting this @jakirkham !
It is very likely that the current package version for this feedstock is out of date. Notes for merging this PR:
license_file
is packagedNote that 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.
NEW: If you want these PRs to be merged automatically, make an issue with code>@conda-forge-admin,</code
please add bot automerge
in the title and merge the resulting PR. This command will add our new bot automerge feature to your feedstock!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 theconda-forge-admin
add it for you.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. 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! This PR was generated by https://circleci.com/gh/regro/circle_worker/43042, please use this URL for debuggingHere is a list of all the pending dependencies (and their versions) for this repo. Please double check all dependencies before merging.
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 yourconda-forge.yml
. If you encounter issues with this feature please ping the bot teamconda-forge/bot
.Analysis of the source code shows a discrepancy between the library's imports and the package's stated requirements in the meta.yaml.
Packages found by inspection but not in the meta.yaml: