1
88%
main: 88%

Ran 14 Aug 2025 08:18PM UTC

Files 839

Run time 30s

Badge

Embed ▾

Committed 14 Aug 2025 07:39PM UTC coverage: 88.259% (+0.01%) from 88.248%

Job # 16974980041.1

Build Type

push

github

Committed by

web-flow

Commit Message

Correctly handle target with global 1q or 3q gates in Sabre (#14715)

* Correctly handle target with global 1q or 3q gates in Sabre

The recently merged #14317 the sabre passes were updated to build a
coupling graph from a target in Rust as part of moving all the passes'
logic into rust. There was a small oversight in the construction of the
coupling graph when handling targets that contain globally defined
operations. Previously, the constructed connectivity graph would treat
the presence of any globally defined operation in the target as meaning
the target had all to all connectivity which isn't always the case. If
the globally defined gate is a 1q operation there could still be a
connectivity graph. Similarly in the presence of > 2q gates in the
target the python version didn't invalidate the construction of a
connectivity graph unless there were no 2q operations. Instead the
connectivity graph was ignoring the multiqubit operations. This commit
updates the logic to match what is done in the Python space
`Target.build_coupling_map()`.

* Store graph of 2q target component in MultiQ error

Run Details

87863 of 99551 relevant lines covered (88.26%)

505349.31 hits per line

Qiskit / qiskit / 16974980041 / 1
88%
main: 88%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 16974980041.1

Qiskit / qiskit / 16974980041 / 1 88% main: 88%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 16974980041.1

Qiskit / qiskit / 16974980041 / 1
88%
main: 88%

README BADGES
x