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

Changed to install qiskit not qiskit-terra #58

Merged
merged 1 commit into from
Feb 23, 2024

Conversation

woodsp-ibm
Copy link
Member

@woodsp-ibm woodsp-ibm commented Feb 16, 2024

Summary

It seems the CI actions and workflows had not been updated and still referred to and installed qiskit-terra. That is no longer part of Qiskit 1.0 and so it installed a pre-1.0 version where qiskit-terra was still there. Later it ended up installing Qiskit 1.0 and with both in the same environment things failed.

I changed the actions to no longer refer to anything as Terra and install Qiskit only.

Details and comments

Probably want to backport this to keep the stable branch running too.

@woodsp-ibm woodsp-ibm added the type: ci Related to CI changes label Feb 16, 2024
@woodsp-ibm
Copy link
Member Author

This is now working better - but failing since stable released Nature is not compatible with Qiskit 1.0 in terms of using the qiskit.tools parallel_map function which was moved etc

@woodsp-ibm woodsp-ibm added the stable backport potential The bug might be minimal and/or import enough to be port to stable label Feb 18, 2024
Copy link
Member

@mrossinek mrossinek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we install Qiskit separately in the first place? It should just pull this in as an indirect dependency when installing qiskit-nature should it not?
I don't see a reason for keeping this around in this form in the first place.

@woodsp-ibm
Copy link
Member Author

I updated things as they were and changed qiskit-terra to qiskit. As the requirements do not call out qiskit explictly that could be possible what you say, but it still has all that stuff in there that allows it to be run off of main branches for either, not only stable. Could one simplify the CI here further - I imagine, I just updated what was there.

@coveralls
Copy link

Pull Request Test Coverage Report for Build 7937030412

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 80.571%

Totals Coverage Status
Change from base Build 7893470074: 0.0%
Covered Lines: 141
Relevant Lines: 175

💛 - Coveralls

@mrossinek mrossinek merged commit f9a6909 into qiskit-community:main Feb 23, 2024
11 checks passed
mergify bot pushed a commit that referenced this pull request Feb 23, 2024
mrossinek pushed a commit that referenced this pull request Feb 23, 2024
(cherry picked from commit f9a6909)

Co-authored-by: Steve Wood <[email protected]>
@woodsp-ibm woodsp-ibm deleted the update_ci branch February 23, 2024 13:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stable backport potential The bug might be minimal and/or import enough to be port to stable type: ci Related to CI changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants