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

Consider unit in Delay comparisons (backport #13816) #13827

Merged
merged 1 commit into from
Feb 11, 2025

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Feb 11, 2025

The unit field was previously ignored, allowing delays in dt units to compare equal to those in s. This commit does not add additional on-the-fly unit conversion to the comparison: if the user specified durations in different time multiples, they may have had a reason to consider them non-equal. This could be revisiting after the new system for duration handling lands (i.e. the new functionality for stretch and other delayed scheduling).

Summary

Details and comments

Fix #13812.


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

The `unit` field was previously ignored, allowing delays in `dt` units
to compare equal to those in `s`. This commit does not add additional
on-the-fly unit conversion to the comparison: if the user specified
durations in different time multiples, they may have had a reason to
consider them non-equal.  This could be revisiting after the new system
for duration handling lands (i.e. the new functionality for `stretch`
and other delayed scheduling).

(cherry picked from commit 32eae98)
@mergify mergify bot requested a review from a team as a code owner February 11, 2025 19:49
@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 following people are relevant to this code:

  • @Qiskit/terra-core

@github-actions github-actions bot added the Changelog: Bugfix Include in the "Fixed" section of the changelog label Feb 11, 2025
@github-actions github-actions bot added this to the 1.3.3 milestone Feb 11, 2025
@jakelishman jakelishman added this pull request to the merge queue Feb 11, 2025
Merged via the queue into stable/1.3 with commit 1c2e6de Feb 11, 2025
20 checks passed
@coveralls
Copy link

Pull Request Test Coverage Report for Build 13271285349

Details

  • 2 of 2 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall first build on mergify/bp/stable/1.3/pr-13816 at 88.902%

Totals Coverage Status
Change from base Build 13264697683: 88.9%
Covered Lines: 79152
Relevant Lines: 89033

💛 - Coveralls

@mtreinish mtreinish deleted the mergify/bp/stable/1.3/pr-13816 branch February 19, 2025 20:57
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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants