Understand the failure.
Verify the repair.
Small, reproducible software failures. The broken implementation, the fix that didn’t work, and the one that passed—preserved together.
Explore the cases ↓How results are verified ↗WHAT THE ARCHIVE CONTAINS
100840 executable cases. 20168 are open.
Every case records the implementation that fails, the fix that did not work, and the repair that passed its checks—with recorded outputs and source hashes. This release adds 100840 cases across 20168 failure mechanisms and 254 domains.
The open tier gives you the failure and the unsuccessful fix for one case in every mechanism. The remaining 80672 cases, 5 variants per mechanism, are member-only: the verified repair, its recorded checks, and the full fixture suite are held in the member archive. Read the methodology ↗
A RECORD OF WHAT WENT WRONG
Browse the archive / 100840
Tableau CNOT propagates Z forward instead of backward · case 01
A Z stabilizer on the target is not copied onto the control, so a Bell state reports +XX, +ZI instead of +XX, +ZZ.
Tableau CNOT propagates Z forward instead of backward · case 02
A Z stabilizer on the target is not copied onto the control, so a Bell state reports +XX, +ZI instead of +XX, +ZZ.
Tableau CNOT propagates Z forward instead of backward · case 03
A Z stabilizer on the target is not copied onto the control, so a Bell state reports +XX, +ZI instead of +XX, +ZZ.
Tableau CNOT propagates Z forward instead of backward · case 04
A Z stabilizer on the target is not copied onto the control, so a Bell state reports +XX, +ZI instead of +XX, +ZZ.
Tableau CNOT propagates Z forward instead of backward · case 05
A Z stabilizer on the target is not copied onto the control, so a Bell state reports +XX, +ZI instead of +XX, +ZZ.
Tableau CNOT copies X from target to control · case 01
After H on qubit 0 and CNOT(0,1) the generator is reported as +XI instead of +XX.
Tableau CNOT copies X from target to control · case 02
After H on qubit 0 and CNOT(0,1) the generator is reported as +XI instead of +XX.
Tableau CNOT copies X from target to control · case 03
After H on qubit 0 and CNOT(0,1) the generator is reported as +XI instead of +XX.
Tableau CNOT copies X from target to control · case 04
After H on qubit 0 and CNOT(0,1) the generator is reported as +XI instead of +XX.
Tableau CNOT copies X from target to control · case 05
After H on qubit 0 and CNOT(0,1) the generator is reported as +XI instead of +XX.
Tableau X gate flips signs of X-type generators · case 01
X on |0> leaves the stabilizer +Z instead of -Z.
Tableau X gate flips signs of X-type generators · case 02
X on |0> leaves the stabilizer +Z instead of -Z.
Tableau X gate flips signs of X-type generators · case 03
X on |0> leaves the stabilizer +Z instead of -Z.
Tableau X gate flips signs of X-type generators · case 04
X on |0> leaves the stabilizer +Z instead of -Z.
Tableau X gate flips signs of X-type generators · case 05
X on |0> leaves the stabilizer +Z instead of -Z.
Depth scheduler treats an empty barrier as a no-op · case 01
A bare barrier after deep work on qubit 0 does not delay a following gate on qubit 2.
Depth scheduler treats an empty barrier as a no-op · case 02
A bare barrier after deep work on qubit 0 does not delay a following gate on qubit 2.
Depth scheduler treats an empty barrier as a no-op · case 03
A bare barrier after deep work on qubit 0 does not delay a following gate on qubit 2.
Depth scheduler treats an empty barrier as a no-op · case 04
A bare barrier after deep work on qubit 0 does not delay a following gate on qubit 2.
Depth scheduler treats an empty barrier as a no-op · case 05
A bare barrier after deep work on qubit 0 does not delay a following gate on qubit 2.
Depth scheduler only waits on the first qubit of a gate · case 01
A CNOT whose target is still busy is placed in the same layer as the target work.
Depth scheduler only waits on the first qubit of a gate · case 02
A CNOT whose target is still busy is placed in the same layer as the target work.
Depth scheduler only waits on the first qubit of a gate · case 03
A CNOT whose target is still busy is placed in the same layer as the target work.
Depth scheduler only waits on the first qubit of a gate · case 04
A CNOT whose target is still busy is placed in the same layer as the target work.
Depth scheduler only waits on the first qubit of a gate · case 05
A CNOT whose target is still busy is placed in the same layer as the target work.
Depth scheduler counts identity gates as layers · case 01
Two id gates on a qubit add two layers of depth.
Depth scheduler counts identity gates as layers · case 02
Two id gates on a qubit add two layers of depth.
Depth scheduler counts identity gates as layers · case 03
Two id gates on a qubit add two layers of depth.
Depth scheduler counts identity gates as layers · case 04
Two id gates on a qubit add two layers of depth.
Depth scheduler counts identity gates as layers · case 05
Two id gates on a qubit add two layers of depth.
Depth scheduler ignores the clbit a conditioned gate reads · case 01
A gate conditioned on c0 is scheduled in parallel with the measurement that writes c0.
Depth scheduler ignores the clbit a conditioned gate reads · case 02
A gate conditioned on c0 is scheduled in parallel with the measurement that writes c0.
Depth scheduler ignores the clbit a conditioned gate reads · case 03
A gate conditioned on c0 is scheduled in parallel with the measurement that writes c0.
Depth scheduler ignores the clbit a conditioned gate reads · case 04
A gate conditioned on c0 is scheduled in parallel with the measurement that writes c0.
Depth scheduler ignores the clbit a conditioned gate reads · case 05
A gate conditioned on c0 is scheduled in parallel with the measurement that writes c0.
Depth scheduler records clbit levels only for measurements · case 01
A measurement into c0 issued after a gate conditioned on c0 is placed before that read completes.
Depth scheduler records clbit levels only for measurements · case 02
A measurement into c0 issued after a gate conditioned on c0 is placed before that read completes.
Depth scheduler records clbit levels only for measurements · case 03
A measurement into c0 issued after a gate conditioned on c0 is placed before that read completes.
Depth scheduler records clbit levels only for measurements · case 04
A measurement into c0 issued after a gate conditioned on c0 is placed before that read completes.
Depth scheduler records clbit levels only for measurements · case 05
A measurement into c0 issued after a gate conditioned on c0 is placed before that read completes.
Depth scheduler charges a layer for every barrier · case 01
Adding a barrier to a circuit increases its reported depth by one.
Depth scheduler charges a layer for every barrier · case 02
Adding a barrier to a circuit increases its reported depth by one.
Depth scheduler charges a layer for every barrier · case 03
Adding a barrier to a circuit increases its reported depth by one.
Depth scheduler charges a layer for every barrier · case 04
Adding a barrier to a circuit increases its reported depth by one.
Depth scheduler charges a layer for every barrier · case 05
Adding a barrier to a circuit increases its reported depth by one.
Direction fixer treats couplers as undirected · case 01
A CNOT against the native direction is emitted unchanged and would be rejected by the device.
Direction fixer treats couplers as undirected · case 02
A CNOT against the native direction is emitted unchanged and would be rejected by the device.
Direction fixer treats couplers as undirected · case 03
A CNOT against the native direction is emitted unchanged and would be rejected by the device.
Direction fixer treats couplers as undirected · case 04
A CNOT against the native direction is emitted unchanged and would be rejected by the device.
Direction fixer treats couplers as undirected · case 05
A CNOT against the native direction is emitted unchanged and would be rejected by the device.
Direction fixer wraps Hadamards around the unflipped CNOT · case 01
A reversed CNOT is emitted as h c, h t, cx c t, h c, h t, still in the non-native direction.
Direction fixer wraps Hadamards around the unflipped CNOT · case 02
A reversed CNOT is emitted as h c, h t, cx c t, h c, h t, still in the non-native direction.
Direction fixer wraps Hadamards around the unflipped CNOT · case 03
A reversed CNOT is emitted as h c, h t, cx c t, h c, h t, still in the non-native direction.
Direction fixer wraps Hadamards around the unflipped CNOT · case 04
A reversed CNOT is emitted as h c, h t, cx c t, h c, h t, still in the non-native direction.
Direction fixer wraps Hadamards around the unflipped CNOT · case 05
A reversed CNOT is emitted as h c, h t, cx c t, h c, h t, still in the non-native direction.
Direction fixer reports self-targeting CNOT as unroutable · case 01
cx 2 2 is reported as ["unroutable", i] instead of ["invalid", i], hiding a malformed circuit behind a hardware message.
Direction fixer reports self-targeting CNOT as unroutable · case 02
cx 2 2 is reported as ["unroutable", i] instead of ["invalid", i], hiding a malformed circuit behind a hardware message.
Direction fixer reports self-targeting CNOT as unroutable · case 03
cx 2 2 is reported as ["unroutable", i] instead of ["invalid", i], hiding a malformed circuit behind a hardware message.
Direction fixer reports self-targeting CNOT as unroutable · case 04
cx 2 2 is reported as ["unroutable", i] instead of ["invalid", i], hiding a malformed circuit behind a hardware message.
Direction fixer reports self-targeting CNOT as unroutable · case 05
cx 2 2 is reported as ["unroutable", i] instead of ["invalid", i], hiding a malformed circuit behind a hardware message.
Direction fixer cancels adjacent Hadamards on different qubits · case 01
h 0 followed by h 1 is deleted entirely.
Direction fixer cancels adjacent Hadamards on different qubits · case 02
h 0 followed by h 1 is deleted entirely.
Direction fixer cancels adjacent Hadamards on different qubits · case 03
h 0 followed by h 1 is deleted entirely.
Direction fixer cancels adjacent Hadamards on different qubits · case 04
h 0 followed by h 1 is deleted entirely.
Direction fixer cancels adjacent Hadamards on different qubits · case 05
h 0 followed by h 1 is deleted entirely.
Direction fixer reports the output position of an unroutable CNOT · case 01
For an unroutable gate at input position 1 the error names position 5 after an earlier flip expanded the output.
Direction fixer reports the output position of an unroutable CNOT · case 02
For an unroutable gate at input position 1 the error names position 5 after an earlier flip expanded the output.
Direction fixer reports the output position of an unroutable CNOT · case 03
For an unroutable gate at input position 1 the error names position 5 after an earlier flip expanded the output.
Direction fixer reports the output position of an unroutable CNOT · case 04
For an unroutable gate at input position 1 the error names position 5 after an earlier flip expanded the output.
Direction fixer reports the output position of an unroutable CNOT · case 05
For an unroutable gate at input position 1 the error names position 5 after an earlier flip expanded the output.
Bloch vector conjugates the |1> amplitude · case 01
The |+i> state is drawn at y = -1.
Bloch vector conjugates the |1> amplitude · case 02
The |+i> state is drawn at y = -1.
Bloch vector conjugates the |1> amplitude · case 03
The |+i> state is drawn at y = -1.
Bloch vector conjugates the |1> amplitude · case 04
The |+i> state is drawn at y = -1.
Bloch vector conjugates the |1> amplitude · case 05
The |+i> state is drawn at y = -1.
Bloch vector puts |0> at the south pole · case 01
|0> is reported with z = -1.
Bloch vector puts |0> at the south pole · case 02
|0> is reported with z = -1.
Bloch vector puts |0> at the south pole · case 03
|0> is reported with z = -1.
Bloch vector puts |0> at the south pole · case 04
|0> is reported with z = -1.
Bloch vector puts |0> at the south pole · case 05
|0> is reported with z = -1.
Bloch vector omits the factor 2 on coherences · case 01
|+> is reported at x = 0.5, inside the sphere, although it is a pure state.
Bloch vector omits the factor 2 on coherences · case 02
|+> is reported at x = 0.5, inside the sphere, although it is a pure state.
Bloch vector omits the factor 2 on coherences · case 03
|+> is reported at x = 0.5, inside the sphere, although it is a pure state.
Bloch vector omits the factor 2 on coherences · case 04
|+> is reported at x = 0.5, inside the sphere, although it is a pure state.
Bloch vector omits the factor 2 on coherences · case 05
|+> is reported at x = 0.5, inside the sphere, although it is a pure state.
Bloch vector normalizes by the norm instead of the squared norm · case 01
The unnormalized input 3|0> + 4|1> yields a vector of length 5 instead of 1.
Bloch vector normalizes by the norm instead of the squared norm · case 02
The unnormalized input 3|0> + 4|1> yields a vector of length 5 instead of 1.
Bloch vector normalizes by the norm instead of the squared norm · case 03
The unnormalized input 3|0> + 4|1> yields a vector of length 5 instead of 1.
Bloch vector normalizes by the norm instead of the squared norm · case 04
The unnormalized input 3|0> + 4|1> yields a vector of length 5 instead of 1.
Bloch vector normalizes by the norm instead of the squared norm · case 05
The unnormalized input 3|0> + 4|1> yields a vector of length 5 instead of 1.
Bloch vector only rejects an exactly zero state · case 01
Amplitudes of order 1e-7 (numerical noise) are blown up into a unit Bloch vector instead of "zero-state".
Bloch vector only rejects an exactly zero state · case 02
Amplitudes of order 1e-7 (numerical noise) are blown up into a unit Bloch vector instead of "zero-state".
Bloch vector only rejects an exactly zero state · case 03
Amplitudes of order 1e-7 (numerical noise) are blown up into a unit Bloch vector instead of "zero-state".
Bloch vector only rejects an exactly zero state · case 04
Amplitudes of order 1e-7 (numerical noise) are blown up into a unit Bloch vector instead of "zero-state".
Bloch vector only rejects an exactly zero state · case 05
Amplitudes of order 1e-7 (numerical noise) are blown up into a unit Bloch vector instead of "zero-state".
Reduced density matrix matches on the kept qubit instead of the environment · case 01
A Bell state reduces to a matrix with coherences instead of the maximally mixed I/2.
Reduced density matrix matches on the kept qubit instead of the environment · case 02
A Bell state reduces to a matrix with coherences instead of the maximally mixed I/2.
Reduced density matrix matches on the kept qubit instead of the environment · case 03
A Bell state reduces to a matrix with coherences instead of the maximally mixed I/2.
Reduced density matrix matches on the kept qubit instead of the environment · case 04
A Bell state reduces to a matrix with coherences instead of the maximally mixed I/2.
Reduced density matrix matches on the kept qubit instead of the environment · case 05
A Bell state reduces to a matrix with coherences instead of the maximally mixed I/2.
INSPECTABLE BY DESIGN
Every result has a runnable source.
Runnable implementations with recorded outputs, source hashes, and explicit contracts. Related variants share a failure mechanism and belong together in evaluation splits.
Read the methodology ↗