Constrain qiskit-aer==0.12.2#11120
Merged
Merged
Conversation
The 0.13.0 release of qiskit-aer causes several test failures, some of which look like changes in the randomisation, and some of which look like true failures. These need a proper resolution, but it's more work than can be easily attached to a PR that's just meant to get CI rolling again.
Collaborator
|
One or more of the the following people are requested to review this:
|
mtreinish
approved these changes
Oct 26, 2023
mergify Bot
pushed a commit
that referenced
this pull request
Oct 26, 2023
The 0.13.0 release of qiskit-aer causes several test failures, some of which look like changes in the randomisation, and some of which look like true failures. These need a proper resolution, but it's more work than can be easily attached to a PR that's just meant to get CI rolling again. (cherry picked from commit 22f4c93)
Member
Author
|
@Mergifyio backport stable/0.25 (I need this to get the translations redeployed from that stable branch.) |
Contributor
✅ Backports have been createdDetails
|
mergify Bot
pushed a commit
that referenced
this pull request
Oct 26, 2023
The 0.13.0 release of qiskit-aer causes several test failures, some of which look like changes in the randomisation, and some of which look like true failures. These need a proper resolution, but it's more work than can be easily attached to a PR that's just meant to get CI rolling again. (cherry picked from commit 22f4c93)
github-merge-queue Bot
pushed a commit
that referenced
this pull request
Oct 26, 2023
The 0.13.0 release of qiskit-aer causes several test failures, some of which look like changes in the randomisation, and some of which look like true failures. These need a proper resolution, but it's more work than can be easily attached to a PR that's just meant to get CI rolling again. (cherry picked from commit 22f4c93) Co-authored-by: Jake Lishman <jake.lishman@ibm.com>
github-merge-queue Bot
pushed a commit
that referenced
this pull request
Oct 27, 2023
The 0.13.0 release of qiskit-aer causes several test failures, some of which look like changes in the randomisation, and some of which look like true failures. These need a proper resolution, but it's more work than can be easily attached to a PR that's just meant to get CI rolling again. (cherry picked from commit 22f4c93) Co-authored-by: Jake Lishman <jake.lishman@ibm.com>
This file contains hidden or 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
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
The 0.13.0 release of qiskit-aer causes several test failures, some of which look like changes in the randomisation, and some of which look like true failures. These need a proper resolution, but it's more work than can be easily attached to a PR that's just meant to get CI rolling again.
Details and comments
Aer 0.13.0 caused several problems for Terra CI, several of which appear to be real problems that we need to fix. #11119 is one of these, but adding to this, there are new test failures from simulator randomness changes, new exceptions coming from noise-model construction (in
QuantumInstance, by the looks of things), and some of Terra's automated tests are wildly overzealous in attempting to discoverGateandControlledGatesubclasses to run over.