Skip to content
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

Rebuild for python 3.13 #152

Merged

Conversation

regro-cf-autotick-bot
Copy link
Contributor

This PR has been triggered in an effort to update python313.

Notes and instructions for merging this PR:

  1. Please merge the PR only after the tests have passed.
  2. Feel free to push to the bot's branch to update this PR if needed.

Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.


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 @conda-forge-admin, please rerun bot in a PR comment to have the conda-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. 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/13039528494 - please use this URL for debugging.

@conda-forge-admin
Copy link
Contributor

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/meta.yaml) and found it was in an excellent condition.

@henryiii
Copy link
Contributor

The ARM failures might be due to a binfmt bug: pypa/cibuildwheel#2257

@jakirkham
Copy link
Member

Thanks Henry! 🙏

Looks like a couple Linux x86_64 native builds also fail

Though interestingly only Python 3.10 and 3.11. Not the Python 3.13 being added

@uis246
Copy link

uis246 commented Feb 10, 2025

Looks like a couple Linux x86_64 native builds also fail

Which ones? All failed checks are either aarch64 or ppc64le.

@henryiii
Copy link
Contributor

henryiii commented Feb 10, 2025

I think it's "tests didn't finish before timeout" that I'm seeing after rerunning. Though some tests are segfaulting.

Running all the tests except long_running
Running: catchsegv python -m numba.runtests -b -m 2 -- 

I thought we are skipping tests one these two platforms, actually.

@henryiii
Copy link
Contributor

henryiii commented Feb 10, 2025

This is getting the wrong architecture. It's not setting archstr=`uname -m` correctly, that's set to the host instead now.

@@ -17,7 +17,7 @@ cxx_compiler:
cxx_compiler_version:
- '13'
docker_image:
- quay.io/condaforge/linux-anvil-ppc64le:alma9
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are these images changing?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The images change to match the build architecture when using cross-compiling

build_platform:
linux_aarch64: linux_64
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this trying to cross-compile instead of emulate now?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know how to build with emulation now, but let's see if we can handle cross-compilation first.

Not sure why we run the tests in the build step.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes this is how cross-compilation is configured

@henryiii
Copy link
Contributor

@jakirkham okay with this? I think longer-term we should move the tests to a test step, and maybe try running a few when cross-compiling; I'd assume the test step runs in emulation.

@henryiii
Copy link
Contributor

The imports work and we don't have any tests working in emulation anyway, so let's go with this, and improve later if needed.

@henryiii henryiii merged commit b34a0b3 into conda-forge:main Feb 10, 2025
27 checks passed
@regro-cf-autotick-bot regro-cf-autotick-bot deleted the rebuild-python313-0-1_h0f7ef5 branch February 10, 2025 21:53
@jakirkham
Copy link
Member

@jakirkham okay with this? I think longer-term we should move the tests to a test step, and maybe try running a few when cross-compiling; I'd assume the test step runs in emulation.

Meaning moving to cross-compilation? Yes think that is ok

Emulation can be kind of slow

Ideally we would add the tests as emulated. Though this can be a bit tricky to setup right

@chrisburr
Copy link
Member

Ideally we would add the tests as emulated. Though this can be a bit tricky to setup right

Doesn't this happen by default when cross-compiling?

@henryiii
Copy link
Contributor

It should if the tests are in the test step. Ours are in the build step for some reason.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants