• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

Qiskit / qiskit / 27707955415
88%
main: 88%

Build:
Build:
LAST BUILD BRANCH: docs-3436-transpiler-passes-examples
DEFAULT BRANCH: main
Ran 17 Jun 2026 06:06PM UTC
Jobs 1
Files 948
Run time 3min
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

17 Jun 2026 05:36PM UTC coverage: 87.549% (+0.02%) from 87.531%
27707955415

push

github

web-flow
Var-based measurement experiments (#16273)

* Initial exploratory support for measuring to Var-indexed clbit and usage of Uint var in for loops

* Linting, test fix

* Remove the simulator - it cannot be used to test circuits with `store` instructions

* Linting

* Overhaul

* Small fixes

* A quick solution to the qpy problem

* DAG comparision fix

* Remove irrelevant test; the qasm3 and the qpy test are the ones needed

* Writing/Reading the LoopParam var by explicitly looking inside the nested circuit

* Use `input` var as for-loop `Var` parameters

Semantically, the loop parameter of a for loop isn't a local-scope
variable of the block body, because otherwise there'd be no way to refer
to how the value is "set" from one iteration of the loop to the other.
Instead, it's owned by the implicit "header" of the loop that deals with
assigning the iteration, and then input into the loop body.

As well as the semantic benefit, relaxing the circuit data model to
permit this makes it cleaner to re-infer from a `ForLoopOp` body what
the loop parameter is in other cases, like QPY.

* Use `input`-Var inference in QPY

This reduces the additional data and semantics that need to be
transmitted through QPY for `ForLoopOp`; the circuit data model only
permits an `input` var in a body in the case of an `expr.Var` parameter,
and the length must be exactly one in that case.

* Small fixes

* Linting

* Return the reader code that was dropped in the merge

* Release note and cleanup of leftovers I thought were already removed

* Fixes according to PR review

* Test fixes

---------

Co-authored-by: Jake Lishman <jake.lishman@ibm.com>

74 of 95 new or added lines in 14 files covered. (77.89%)

7 existing lines in 4 files now uncovered.

111575 of 127443 relevant lines covered (87.55%)

1006558.4 hits per line

Uncovered Changes

Lines Coverage ∆ File
12
77.0
-0.44% crates/qpy/src/circuit_reader.rs
3
96.34
-3.66% qiskit/circuit/controlflow/for_loop.py
2
92.71
-0.08% crates/qpy/src/circuit_writer.rs
1
85.32
0.0% crates/circuit/src/dag_circuit.rs
1
83.76
0.07% crates/circuit/src/operations.rs
1
98.18
-1.82% qiskit/circuit/controlflow/box.py
1
91.3
-0.18% qiskit/circuit/controlflow/builder.py

Coverage Regressions

Lines Coverage ∆ File
4
74.14
-0.16% crates/circuit/src/parameter/symbol_expr.rs
1
90.36
0.0% crates/circuit/src/parameter/parameter_expression.rs
1
92.29
1.29% crates/qasm2/src/lex.rs
1
94.46
-0.01% qiskit/circuit/quantumcircuit.py
Jobs
ID Job ID Ran Files Coverage
1 27707955415.1 17 Jun 2026 06:06PM UTC 948
87.55
GitHub Action Run
Source Files on build 27707955415
  • Tree
  • List 948
  • Changed 21
  • Source Changed 15
  • Coverage Changed 21
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #27707955415
  • 0b156c49 on github
  • Prev Build on gh-readonly-queue/main/pr-14912-56d8e04de08f5b170b8d9481c61bb1ff41b9bce6 (#27684886112)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc