Repo Added
|
Files
868
|
Badge
README BADGES
|
push
github
Fix tracking of routing permutation in Sabre with disjoint backends (#13833) (#13835) If the backing coupling graph is disjoint, and unused components of the coupling graph would not be considered when constructing the complete routing permutation. In practice, Sabre aborts immediately after layout without attempting to route, if it needed to split the DAG across more than one disjoint component, because it can't guarantee correctness of the final routing in the presence of component-spanning barriers or classical communication, so the only way for a component to be forgotten is if the backend is disjoint, but the DAG fits into a single component. (cherry picked from commit b93317983) Co-authored-by: Jake Lishman <jake.lishman@ibm.com>
6 of 6 new or added lines in 1 file covered. (100.0%)
9 existing lines in 3 files now uncovered.79163 of 89039 relevant lines covered (88.91%)
357251.11 hits per line
Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line |
---|