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

Constrain numpy in tests #1203

Merged
merged 23 commits into from
Jun 20, 2023
Merged

Constrain numpy in tests #1203

merged 23 commits into from
Jun 20, 2023

Conversation

eggerdj
Copy link
Contributor

@eggerdj eggerdj commented Jun 19, 2023

Summary

Numpy released a new version which has caused our tests to fail. See here for example in Terra: Qiskit/qiskit#10305

Details and comments

This PR constrains the version of numpy in the tests. We will need to Qiskit to align with the new numpy.

eggerdj and others added 23 commits April 29, 2022 14:55
@eggerdj
Copy link
Contributor Author

eggerdj commented Jun 19, 2023

Short-term solution to #1204

@coruscating
Copy link
Collaborator

We usually pin package versions directly in requirements.txt rather than using a separate file to pin tests only. The question is whether we're okay with potential users using numpy 1.25 with experiments. It seems that there may be actual incompatibilities between Terra and 1.25 beyond the deprecation warnings, so I think it's better to pin the version in requirements.txt directly.

@eggerdj
Copy link
Contributor Author

eggerdj commented Jun 19, 2023

I don't have any strong opinions on this topic. I chose this approach to align with Terra. See here: Qiskit/qiskit#10306 Deviating from that approach is fine by me.

@coruscating coruscating added this pull request to the merge queue Jun 19, 2023
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jun 19, 2023
@coruscating coruscating added this pull request to the merge queue Jun 19, 2023
Merged via the queue into qiskit-community:main with commit a8142f1 Jun 20, 2023
@eggerdj eggerdj deleted the pin_numpy branch June 20, 2023 06:48
@coruscating coruscating added the backport stable potential The issue or PR might be minimal and/or import enough to backport to stable label Jun 29, 2023
mergify bot pushed a commit that referenced this pull request Jun 29, 2023
### Summary

Numpy released a new version which has caused our tests to fail. See
here for example in Terra:
Qiskit/qiskit#10305

### Details and comments

This PR constrains the version of numpy in the tests. We will need to
Qiskit to align with the new numpy.

(cherry picked from commit a8142f1)
coruscating pushed a commit that referenced this pull request Jun 29, 2023
This is an automatic backport of pull request #1203 done by
[Mergify](https://mergify.com).


---


<details>
<summary>Mergify commands and options</summary>

<br />

More conditions and actions can be found in the
[documentation](https://docs.mergify.com/).

You can also trigger Mergify actions by commenting on this pull request:

- `@Mergifyio refresh` will re-evaluate the rules
- `@Mergifyio rebase` will rebase this PR on its base branch
- `@Mergifyio update` will merge the base branch into this PR
- `@Mergifyio backport <destination>` will backport this PR on
`<destination>` branch

Additionally, on Mergify [dashboard](https://dashboard.mergify.com) you
can:

- look at your merge queues
- generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com
</details>

Co-authored-by: Daniel J. Egger <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport stable potential The issue or PR might be minimal and/or import enough to backport to stable
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants