Add initial qiskit-neko CI job #1422
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In Qiskit/qiskit-neko#41 we're updating the default simulator backend plugin used by qiskit-neko to rely on the fake backends provider in the qiskit-ibm-runtime project. A key aspect of qiskit-neko is the reciprocity of testing to maintain compatibility in the qiskit ecosystem (see: https://github.com/Qiskit/qiskit-neko?tab=readme-ov-file#downstream-usage-in-testing) so to ensure this is maintainable and the interface remains compatible for every project using neko this commit adds a corresponding job to exercise the qiskit-ibm-runtime usage in the tests. However, this is blocked until after Qiskit/qiskit-neko#41 merges as that is needed to fix the test suite. A followup will be needed to add a backend selection to the action configuration so that we can actually use a fake backend. A longer term step we should investigate is adding a qiskit-neko plugin to the repo which would enable using qiskit-ibm-runtime's backends and primitives directly for integration testing with real backends. But that is much longer term and isn't part of this
Pull Request Test Coverage Report for Build 8019661440Details
💛 - Coveralls |
kt474
approved these changes
Oct 16, 2024
ElePT
reviewed
Oct 17, 2024
There was a problem hiding this comment.
The current neko failure is dues to an incompatibility in qiskit_algorithms with scipy>=1.14, the bug was fixed in main (qiskit-community/qiskit-algorithms@3fb69b3), but neko is pulling the latest released version which doesn't include the fix. I can do a patch release of algorithms, but given the current level of maintenance of the repo, it might make sense considering installing the package from source when running neko.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
In Qiskit/qiskit-neko#41 we're updating the default simulator backend plugin used by qiskit-neko to rely on the fake backends provider in the qiskit-ibm-runtime project. A key aspect of qiskit-neko is the reciprocity of testing to maintain compatibility in the qiskit ecosystem (see:
https://github.com/Qiskit/qiskit-neko?tab=readme-ov-file#downstream-usage-in-testing) so to ensure this is maintainable and the interface remains compatible for every project using neko this commit adds a corresponding job to exercise the qiskit-ibm-runtime usage in the tests. However, this is blocked until after Qiskit/qiskit-neko#41 merges as that is needed to fix the test suite. A followup will be needed to add a backend selection to the action configuration so that we can actually use a fake backend.
A longer term step we should investigate is adding a qiskit-neko plugin to the repo which would enable using qiskit-ibm-runtime's backends and primitives directly for integration testing with real backends. But that is much longer term and isn't part of this commit.
Details and comments