-
-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
numba v0.57.0 #115
numba v0.57.0 #115
Conversation
…nda-forge-pinning 2023.04.28.23.49.10
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 ( |
Failures here are a result of |
The bot has now opened the However CI is encountering some build issues there ( conda-forge/llvmlite-feedstock#69 (comment) ) |
Also do python 3.11 builds need to be added to the config here too? |
Depends on PR ( conda-forge/llvmlite-feedstock#66 ), which in turn depends on PR ( conda-forge/llvmlite-feedstock#69 ) |
@conda-forge-admin, please re-render |
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/numba-feedstock/actions/runs/5019174556. |
The `__init__.py` file here was dropped. Thus it is no longer a Python package. So drop it from `import` tests. numba/numba@0.56.4...0.57.0#diff-a1318af01b8a075eb478c8dc098351f973b7deed0f2ca340c2b61acf7b8bf252
Needed for CUDA 12+ support. Keep `cudatoolkit` for legacy cases where users are not pulling `cuda-version`.
This appears to confuse Numba's test suite in 0.59.0. Given it is a no-op anyways, just drop it. Likely it was leftover when tweaking the number of tests run before. The random selection of tests already used should already be sufficient.
This test is fast. So if it fails, will do so quickly. Run early in the tests to enable faster iteration on related issues.
…nda-forge-pinning 2023.05.17.15.05.36
The `ppc64le` test suite hangs on Travis (and has done so for a few releases now). Perhaps it is just too much for that CI provider to handle. The `aarch64` builds need patches to LLVM to fix some test cases. Those patches are currently in review at that feedstock. So go ahead and skip these tests for now. Can re-enable once patched LLVM builds are released.
echo 'Running only a slice of tests' | ||
$SEGVCATCH python -m numba.runtests -b -j --random='0.15' --exclude-tags='long_running' -m $TEST_NPROCS -- numba.tests | ||
echo "Skipping numba test suite on $archstr" | ||
#echo 'Running only a random selection of tests' | ||
#$SEGVCATCH python -m numba.runtests -b --random='0.15' --exclude-tags='long_running' -m $TEST_NPROCS -- numba.tests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The ppc64le
builds have been hanging in the test suite for a few releases now ( #102 ). It may just be too much for Travis CI to handle. So skipping those.
Also aarch64
needs some patches to LLVM to fix some test issues ( conda-forge/llvmdev-feedstock#192 ). This is in review. Once new patched LLVM packages are shipped, this should be fixed.
Can open a PR to re-enable the skipped tests after. Then merge once the issues are resolved in the LLVM package. Since we use the LLVM dynamic library, no rebuilding of Numba should be needed to get those fixes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Submitted PR ( #119 ) to try reverting
Have applied the Python 3.11 migrator manually here to add those builds |
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! |
It is very likely that the current package version for this feedstock is out of date.
Checklist before merging this PR:
license_file
is packagedInformation about this PR:
@conda-forge-admin,
please add bot automerge
in the title and merge the resulting PR. This command will add our bot automerge feature to your feedstock.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@conda-forge-admin, please rerun bot
in a PR comment to have theconda-forge-admin
add it for you.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 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:
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/4856418928, please use this URL for debugging.
Fixes #110
Fixes #111
Fixes #112
Fixes #116