Skip to content

New Project: rustworkx #82

@IvanIsCoding

Description

@IvanIsCoding

Please describe the project

A high-performance Python graph library implemented in Rust. Among other things, it is used by Qiskit which is an open-source library maintained by IBM Quantum.

URL for the project

https://www.rustworkx.org/
https://github.com/Qiskit/rustworkx

Describe current CI/CD setup

We do not test IBM Power or IBM Z support at all. For releases, we use QEMU. Because our dependencies do not release wheels for these architectures, rustworkx is forced to skip tests. Building our dependencies with QEMU triggers the 6hr time out from GitHub actions.

Describe the primary use case for the Github Action Runner

I want to build and release Python wheels without having to run QEMU.

Paste a link to the existing actions workflow file(s) or directory

https://github.com/Qiskit/rustworkx/blob/main/.github/workflows/wheels.yml is the current release workflow with QEMU for ppc64le and s390x.

How often do you plan on executing the runner?

Every release, which is very infrequent but has a high-impact as the builds break often. I have seriously considered dropping support for ppc64le/s390x entirely.

What is the primary programming language for the project?

Python/Rust

Please select desired hardware

  • Power 9 (ppc64le)
  • IBM Z / LinuxONE (s390x)

Account names of the GitHub repo admins that will need access to setting up the runner

@mtreinish and @jakelishman

Metadata

Metadata

Assignees

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions