-
Notifications
You must be signed in to change notification settings - Fork 3
Description
(Note that this is related to #82.)
Please describe the project
An SDK for quantum programming, compilation and execution.
URL for the project
https://github.com/Qiskit/qiskit
Describe current CI/CD setup
We use GitHub Actions, and do not test on ppc64le or s390x. We do however deploy Python wheels (with compiled Rust components) for these platforms using QEMU, but without running tests because of the excessive runtime cost of the emulation.
Describe the primary use case for the Github Action Runner
We would like to be able to test the wheels before deployment, at least at as part of the deployment procedure (typically around once per month).
Paste a link to the existing actions workflow file(s) or directory
Current wheel builds under emulation are here: https://github.com/Qiskit/qiskit/blob/0b7d00062472dd6dfb544ff5e55b1cb7b8bb63da/.github/workflows/wheels-build.yml#L141-L185
How often do you plan on executing the runner?
At a minimum, every release (approximately once per month, but not necessarily evenly spaced). If usage time is more frequently, potentially daily on a cron job.
What is the primary programming language for the project?
Rust, with Python and C components.
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
- jakelishman
- mtreinish