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

Restore accidently deleted scheduling passes (backport #11184) #11189

Merged
merged 1 commit into from
Nov 3, 2023

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Nov 3, 2023

This is an automatic backport of pull request #11184 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

In #10754 3 legacy scheduling passes were accidently deleted. These
passes were incorrectly identified as deprecated, however they were
never marked as deprecating just pending future deprecation. They were
intended to be be promoted from a pending deprecation to a full
deprecation in #8023 but we never took that step because there were
objections at the time as they still served a purpose. #10754 likely
missed this as the only indication in the deprecation decorator was a
kwarg that said `pending=True`, and this was the only indication that
these passes weren't actually deprecated yet. This commit restores these
passes on the 0.45.0 branch in the interest of unblocking the 0.45.0
release ASAP. We can handle forward porting this PR to main as needed
after the 0.45.0 release is tagged.

(cherry picked from commit aa272e9)
@mergify mergify bot requested a review from a team as a code owner November 3, 2023 09:32
@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

@jakelishman jakelishman enabled auto-merge November 3, 2023 09:34
@jakelishman jakelishman added the Changelog: None Do not include in changelog label Nov 3, 2023
@coveralls
Copy link

Pull Request Test Coverage Report for Build 6743477021

  • 304 of 334 (91.02%) changed or added relevant lines in 7 files are covered.
  • 6 unchanged lines in 2 files lost coverage.
  • Overall coverage increased (+0.08%) to 86.953%

Changes Missing Coverage Covered Lines Changed/Added Lines %
qiskit/transpiler/passes/scheduling/alap.py 59 61 96.72%
qiskit/transpiler/passes/scheduling/asap.py 63 65 96.92%
qiskit/transpiler/passes/scheduling/alignments/align_measures.py 74 78 94.87%
qiskit/transpiler/passes/scheduling/dynamical_decoupling.py 99 121 81.82%
Files with Coverage Reduction New Missed Lines %
crates/qasm2/src/lex.rs 3 91.92%
qiskit/pulse/library/waveform.py 3 93.75%
Totals Coverage Status
Change from base Build 6738287566: 0.08%
Covered Lines: 74377
Relevant Lines: 85537

💛 - Coveralls

@jakelishman jakelishman added this pull request to the merge queue Nov 3, 2023
Merged via the queue into main with commit b32942e Nov 3, 2023
@mergify mergify bot deleted the mergify/bp/main/pr-11184 branch November 3, 2023 12:35
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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants