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

Fix PropertySet re-use in BasePassManager.run (backport #11787) #11863

Merged
merged 1 commit into from
Feb 22, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Feb 22, 2024

This is an automatic backport of pull request #11787 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

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 you can:

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

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

Since the genericised `PassManager`, the `PropertySet` used in the
`WorkflowState` of a pass-manager pipeline was taken directly from the
internal state of the `BasePassManager`.  This is set to a clean
`PropertySet` during the pass-manager initialisation (similar to how it
was in the previous version), but is not reset on subsequent runs.  This
didn't cause problems in the old form because the "iterator" over tasks
in the old form was a new `RunningPassManager` instance.

Failing to generate a clean property set could lead to passes getting
fed old analysis data when the pass manager was used more than once,
leading to miscompilations.

(cherry picked from commit 9c1accb)
@mergify mergify bot requested a review from a team as a code owner February 22, 2024 17:57
@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

@github-actions github-actions bot added Changelog: Bugfix Include in the "Fixed" section of the changelog mod: transpiler Issues and PRs related to Transpiler labels Feb 22, 2024
@github-actions github-actions bot added this to the 1.0.1 milestone Feb 22, 2024
@jakelishman jakelishman modified the milestones: 1.0.1, 0.46.1 Feb 22, 2024
@coveralls
Copy link

Pull Request Test Coverage Report for Build 8008900082

Details

  • 0 of 2 (100.0%) changed or added relevant lines in 1 file are covered.
  • 3 unchanged lines in 1 file lost coverage.
  • Overall coverage increased (+0.001%) to 86.926%

Files with Coverage Reduction New Missed Lines %
crates/qasm2/src/lex.rs 3 91.94%
Totals Coverage Status
Change from base Build 7975926081: 0.001%
Covered Lines: 75065
Relevant Lines: 86355

💛 - Coveralls

@jakelishman jakelishman added this pull request to the merge queue Feb 22, 2024
Merged via the queue into stable/0.46 with commit 31c97a8 Feb 22, 2024
12 of 14 checks passed
@mergify mergify bot deleted the mergify/bp/stable/0.46/pr-11787 branch February 22, 2024 20:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Changelog: Bugfix Include in the "Fixed" section of the changelog mod: transpiler Issues and PRs related to Transpiler
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants