Qiskit / qiskit
90%
main: 89%

LAST BUILD BRANCH: BD-add-alt-text
DEFAULT BRANCH: main
Repo Added
Files 913
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

LAST BUILD ON BRANCH gh-readonly-queue/main/pr-12898-1fdd527f90d420fee4d2c93b4befd83865a06d4b
branch: gh-readonly-queue/main/pr-12898-1fdd527f90d420fee4d2c93b4befd83865a06d4b
CHANGE BRANCH
x

coverage: 89.738% (-0.01%) from 89.751%
10293650667

push

github

web-flow 
Remove init peephole optimization discrete basis check (#12898)

* Fix target handling in discrete basis check

In #12727 a check was added to the default init stage's construction to
avoid running 2q gate consolidation in the presence of targets with
only discrete gates. However the way the target was being used in this
check was incorrect. The name for an instruction in the target should be
used as its identifier and then if we need the object representation
that should query the target for that object based on the name. However
the check was doing this backwards getting a list of operation objects
and then using the name contained in the object. This will cause issues
for instructions that use custom names such as when there are tuned
variants or a custom gate instance with a unique name.

While there is some question over whether we need this check as we will
run the consolidate 2q blocks pass as part of the optimization stage
which will have the same effect, this opts to just fix the target usage
for it to minimize the diff. Also while not the explicit goal of this
check it is protecting against some bugs in the consolidate blocks pass
that occur when custom gates are used. So for the short term this check
is retained, but in the future when these bugs in consolidate blocks are
fixed we can revisit whether we want to remove the conditional logic.

* Remove check and fix ConsolidateBlocks bug

This commit pivots this PR branch to just remove the additional logic
around skipping the optimization passes for discrete basis sets. The
value the check was actually providing was not around a discrete basis
set target and instead was to workaround a bug in the consolidate blocks
pass. If a discrete basis set target was used this would still fail
because we will unconditionally call `ConsolidateBlocks` during the
optimization stage. This commit opts to just remove the extra complexity
of the conditional execution of the peephole optimization passes and
ins... (continued)

9 of 10 new or added lines in 2 files covered. (90.0%)

13 existing lines in 3 files now uncovered.

67319 of 75017 relevant lines covered (89.74%)

388863.43 hits per line

Relevant lines Covered
75017 RELEVANT LINES 67319 COVERED LINES
388863.43 HITS PER LINE
Source Files on gh-readonly-queue/main/pr-12898-1fdd527f90d420fee4d2c93b4befd83865a06d4b

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
10293650667 gh-readonly-queue/main/pr-12898-1fdd527f90d420fee4d2c93b4befd83865a06d4b Remove init peephole optimization discrete basis check (#12898) * Fix target handling in discrete basis check In #12727 a check was added to the default init stage's construction to avoid running 2q gate consolidation in the presence of targets ... push web-flow github
89.74
See All Builds (9023)