-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Update to python-0.9.0 - only unix - with ARM support #10
Conversation
…nda-forge-pinning 2024.07.04.12.04.07
…nda-forge-pinning 2024.07.04.12.04.07
…nda-forge-pinning 2024.07.07.00.25.18
…nda-forge-pinning 2024.07.07.00.25.18
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 ( |
@conda-forge-admin, please rerender |
…nda-forge-pinning 2024.07.07.00.25.18
|
@conda-forge-admin, please rerender |
…nda-forge-pinning 2024.07.07.08.18.48
|
@conda-forge/core The Linux ARM tests timeout - most likely because they require too much memory. I previously had a similar issue on Windows #11 . Is there any way to get access to native ARM builds? |
Before we think about native arm runners, can you try adding azure:
free_disk_space: true
settings_linux:
swapfile_size: 15GiB to |
@conda-forge-admin, please rerender |
…nda-forge-pinning 2024.07.08.21.10.22
@h-vetinari Is there a similar trick for windows to fix the out of memory issue in #11 ? |
We don't have a common interface unfortunately, and windows works... less reliably... but in principle you can do:
This will set a swapfile somewhere between 8GB & 16GB, depending what the system returns. Here's some other related issues: conda-forge/conda-smithy#1949 & conda-forge/conda-smithy#1971 |
@h-vetinari Thanks a lot, based on your suggestion, I was able to successfully build the windows version in #11 and also the ARM version works fine now. |
Checklist
0
(if the version changed)conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)