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

Pin setuptools in CI #8526

Merged
merged 11 commits into from
Aug 12, 2022
Merged

Pin setuptools in CI #8526

merged 11 commits into from
Aug 12, 2022

Conversation

mtreinish
Copy link
Member

Summary

The recently released setuptools 64.0.0 release introduced a regression
that prevents editable installs from working (see pypa/setuptools#3498).
This is blocking CI as we use editable installs to build and install
terra for testing. When there is an upstream release fixing this issue
we can remove the pins.

Details and comments

The recently released setuptools 64.0.0 release introduced a regression
that prevents editable installs from working (see pypa/setuptools#3498).
This is blocking CI as we use editable installs to build and install
terra for testing. When there is an upstream release fixing this issue
we can remove the pins.
@mtreinish mtreinish requested a review from a team as a code owner August 11, 2022 16:11
@qiskit-bot
Copy link
Collaborator

Thank you for opening a new pull request.

Before your PR can be merged it will first need to pass continuous integration tests and be reviewed. Sometimes the review process can be slow, so please be patient.

While you're waiting, please feel free to review other open PRs. While only a subset of people are authorized to approve pull requests for merging, everyone is encouraged to review open pull requests. Doing reviews helps reduce the burden on the core team and helps make the project's code better for everyone.

One or more of the the following people are requested to review this:

  • @Qiskit/terra-core

@agroszer
Copy link

SETUPTOOLS_ENABLE_FEATURES="legacy-editable" helped us

@mtreinish
Copy link
Member Author

@agroszer thanks, I'll give that a try now. I was just trying to avoid needing that in the hope a downgrade/pin would be sufficient. I'm not sure what is causing the previous release to fail now.

@agroszer
Copy link

went down the same rabbithole

@coveralls
Copy link

coveralls commented Aug 11, 2022

Pull Request Test Coverage Report for Build 2842621297

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.003%) to 84.052%

Totals Coverage Status
Change from base Build 2840271885: 0.003%
Covered Lines: 56316
Relevant Lines: 67001

💛 - Coveralls

kevinhartman
kevinhartman previously approved these changes Aug 11, 2022
Copy link
Contributor

@kevinhartman kevinhartman left a comment

Choose a reason for hiding this comment

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

LGTM

@mtreinish mtreinish added type: qa Issues and PRs that relate to testing and code quality automerge Changelog: None Do not include in changelog labels Aug 11, 2022
@Cryoris Cryoris merged commit 82e38d1 into Qiskit:main Aug 12, 2022
@agroszer
Copy link

setuptools 64.0.1 fixes this

mtreinish added a commit to mtreinish/qiskit-core that referenced this pull request Aug 12, 2022
With the release of setuptools 64.0.1 the issues previously blocking CI
and editable installs more generally should have fixed now. This commit
reverts the pins previously introduced to unblock CI and work around the
broken release.

This reverts commit 82e38d1.
@mtreinish mtreinish added the stable backport potential The bug might be minimal and/or import enough to be port to stable label Aug 16, 2022
@mtreinish mtreinish deleted the pin-setuptools branch August 16, 2022 21:42
mergify bot pushed a commit that referenced this pull request Aug 16, 2022
* Pin setuptools in CI

The recently released setuptools 64.0.0 release introduced a regression
that prevents editable installs from working (see pypa/setuptools#3498).
This is blocking CI as we use editable installs to build and install
terra for testing. When there is an upstream release fixing this issue
we can remove the pins.

* Remove pip/setuptools/wheel manual install step

* Try venv instead of virtualenv

* Revert "Try venv instead of virtualenv"

This reverts commit 3ada819.

* Revert "Remove pip/setuptools/wheel manual install step"

This reverts commit 831bc6e.

* Pin in constraints.txt too

* Lower version further

* Pin setuptools-rust too

* Set editable install to legacy mode via env var

* Set env variable correctly everywhere we build terra

* Add missing env variable setting for image tests

(cherry picked from commit 82e38d1)
mergify bot added a commit that referenced this pull request Aug 16, 2022
* Pin setuptools in CI

The recently released setuptools 64.0.0 release introduced a regression
that prevents editable installs from working (see pypa/setuptools#3498).
This is blocking CI as we use editable installs to build and install
terra for testing. When there is an upstream release fixing this issue
we can remove the pins.

* Remove pip/setuptools/wheel manual install step

* Try venv instead of virtualenv

* Revert "Try venv instead of virtualenv"

This reverts commit 3ada819.

* Revert "Remove pip/setuptools/wheel manual install step"

This reverts commit 831bc6e.

* Pin in constraints.txt too

* Lower version further

* Pin setuptools-rust too

* Set editable install to legacy mode via env var

* Set env variable correctly everywhere we build terra

* Add missing env variable setting for image tests

(cherry picked from commit 82e38d1)

Co-authored-by: Matthew Treinish <[email protected]>
mergify bot added a commit that referenced this pull request Aug 22, 2022
* Revert "Pin setuptools in CI (#8526)"

With the release of setuptools 64.0.1 the issues previously blocking CI
and editable installs more generally should have fixed now. This commit
reverts the pins previously introduced to unblock CI and work around the
broken release.

This reverts commit 82e38d1.

* Add back SETUPTOOLS_ENABLE_FEATURES env var for legacy editable install

Co-authored-by: Jake Lishman <[email protected]>
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
mergify bot pushed a commit that referenced this pull request Aug 22, 2022
* Revert "Pin setuptools in CI (#8526)"

With the release of setuptools 64.0.1 the issues previously blocking CI
and editable installs more generally should have fixed now. This commit
reverts the pins previously introduced to unblock CI and work around the
broken release.

This reverts commit 82e38d1.

* Add back SETUPTOOLS_ENABLE_FEATURES env var for legacy editable install

Co-authored-by: Jake Lishman <[email protected]>
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
(cherry picked from commit dfca1fb)
mergify bot added a commit that referenced this pull request Aug 22, 2022
* Revert "Pin setuptools in CI (#8526)"

With the release of setuptools 64.0.1 the issues previously blocking CI
and editable installs more generally should have fixed now. This commit
reverts the pins previously introduced to unblock CI and work around the
broken release.

This reverts commit 82e38d1.

* Add back SETUPTOOLS_ENABLE_FEATURES env var for legacy editable install

Co-authored-by: Jake Lishman <[email protected]>
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
(cherry picked from commit dfca1fb)

Co-authored-by: Matthew Treinish <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Changelog: None Do not include in changelog stable backport potential The bug might be minimal and/or import enough to be port to stable type: qa Issues and PRs that relate to testing and code quality
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants