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

CI: Add linux_qemu action and remove travis testing. #25108

Merged
merged 5 commits into from Nov 11, 2023

Conversation

charris
Copy link
Member

@charris charris commented Nov 11, 2023

This backport includes at least the following PRs from main: #24479, #24657, #24806, and #25089.

The main point of all this is to stop using travis for s390x testing and use the linux_qemu action instead. An added benefit is that more architectures get tested and the 1.26.x branch in more in line with main.

Note that #24806 was already partially backported, but did not use the linux_qemu action.

@charris charris force-pushed the add-qemu-tests branch 2 times, most recently from fa4235c to a9497ce Compare November 11, 2023 04:21
seiko2plus and others added 4 commits November 10, 2023 21:29
  This patch implements cross-compile builds for armhf, ppc64le,
  and IBMZ architectures in the CI pipeline.
  While it might not be highly efficient due to qemu's quirks and slower performance,
  it still does extend testing to include umath, ufunc, and simd operations.

  In this setup, QEMU manages the Python interpreter, meson, and runtime tests, while ninja,
  the toolchain, and any binutils binaries are executed natively to speed up the build.
We can run the s390x tests in linux_qemu.yml.
Backport of numpy#24806.

This backport was already made in numpy#25083, but that didn't make
use of the linux_qemu.yml action, so this tweaks it a bit.
- Skip test that needs huge memory on 32-bit architectures
- Update windows.yml action from main
@charris charris merged commit 29c2030 into numpy:maintenance/1.26.x Nov 11, 2023
50 checks passed
@charris charris deleted the add-qemu-tests branch November 11, 2023 11:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants