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
Inherited observer context overwrites callback-local values · case 01
Inherited observer context overwrites callback-local values; the returned lifecycle plan violates the stated transition contract.
Inherited observer context overwrites callback-local values · case 02
Inherited observer context overwrites callback-local values; the returned lifecycle plan violates the stated transition contract.
Inherited observer context overwrites callback-local values · case 03
Inherited observer context overwrites callback-local values; the returned lifecycle plan violates the stated transition contract.
Inherited observer context overwrites callback-local values · case 04
Inherited observer context overwrites callback-local values; the returned lifecycle plan violates the stated transition contract.
Inherited observer context overwrites callback-local values · case 05
Inherited observer context overwrites callback-local values; the returned lifecycle plan violates the stated transition contract.
A callback-local None fails to shadow inherited context · case 01
A callback-local None fails to shadow inherited context; the returned lifecycle plan violates the stated transition contract.
A callback-local None fails to shadow inherited context · case 02
A callback-local None fails to shadow inherited context; the returned lifecycle plan violates the stated transition contract.
A callback-local None fails to shadow inherited context · case 03
A callback-local None fails to shadow inherited context; the returned lifecycle plan violates the stated transition contract.
A callback-local None fails to shadow inherited context · case 04
A callback-local None fails to shadow inherited context; the returned lifecycle plan violates the stated transition contract.
A callback-local None fails to shadow inherited context · case 05
A callback-local None fails to shadow inherited context; the returned lifecycle plan violates the stated transition contract.
Throwing callback leaves its inner context installed · case 01
Throwing callback leaves its inner context installed; the returned lifecycle plan violates the stated transition contract.
Throwing callback leaves its inner context installed · case 02
Throwing callback leaves its inner context installed; the returned lifecycle plan violates the stated transition contract.
Throwing callback leaves its inner context installed · case 03
Throwing callback leaves its inner context installed; the returned lifecycle plan violates the stated transition contract.
Throwing callback leaves its inner context installed · case 04
Throwing callback leaves its inner context installed; the returned lifecycle plan violates the stated transition contract.
Throwing callback leaves its inner context installed · case 05
Throwing callback leaves its inner context installed; the returned lifecycle plan violates the stated transition contract.
Out-of-order callback completion pops the active sibling trace span · case 01
Out-of-order callback completion pops the active sibling trace span; the returned lifecycle plan violates the stated transition contract.
Out-of-order callback completion pops the active sibling trace span · case 02
Out-of-order callback completion pops the active sibling trace span; the returned lifecycle plan violates the stated transition contract.
Out-of-order callback completion pops the active sibling trace span · case 03
Out-of-order callback completion pops the active sibling trace span; the returned lifecycle plan violates the stated transition contract.
Out-of-order callback completion pops the active sibling trace span · case 04
Out-of-order callback completion pops the active sibling trace span; the returned lifecycle plan violates the stated transition contract.
Out-of-order callback completion pops the active sibling trace span · case 05
Out-of-order callback completion pops the active sibling trace span; the returned lifecycle plan violates the stated transition contract.
Forwarded observer routes erase legitimate nonconsecutive sender revisits · case 01
Forwarded observer routes erase legitimate nonconsecutive sender revisits; the returned lifecycle plan violates the stated transition contract.
Forwarded observer routes erase legitimate nonconsecutive sender revisits · case 02
Forwarded observer routes erase legitimate nonconsecutive sender revisits; the returned lifecycle plan violates the stated transition contract.
Forwarded observer routes erase legitimate nonconsecutive sender revisits · case 03
Forwarded observer routes erase legitimate nonconsecutive sender revisits; the returned lifecycle plan violates the stated transition contract.
Forwarded observer routes erase legitimate nonconsecutive sender revisits · case 04
Forwarded observer routes erase legitimate nonconsecutive sender revisits; the returned lifecycle plan violates the stated transition contract.
Forwarded observer routes erase legitimate nonconsecutive sender revisits · case 05
Forwarded observer routes erase legitimate nonconsecutive sender revisits; the returned lifecycle plan violates the stated transition contract.
Disposed context binding continues to invoke its observer callback · case 01
Disposed context binding continues to invoke its observer callback; the returned lifecycle plan violates the stated transition contract.
Disposed context binding continues to invoke its observer callback · case 02
Disposed context binding continues to invoke its observer callback; the returned lifecycle plan violates the stated transition contract.
Disposed context binding continues to invoke its observer callback · case 03
Disposed context binding continues to invoke its observer callback; the returned lifecycle plan violates the stated transition contract.
Disposed context binding continues to invoke its observer callback · case 04
Disposed context binding continues to invoke its observer callback; the returned lifecycle plan violates the stated transition contract.
Disposed context binding continues to invoke its observer callback · case 05
Disposed context binding continues to invoke its observer callback; the returned lifecycle plan violates the stated transition contract.
A callback context reset token is consumed from the wrong context · case 01
A callback context reset token is consumed from the wrong context; the returned lifecycle plan violates the stated transition contract.
A callback context reset token is consumed from the wrong context · case 02
A callback context reset token is consumed from the wrong context; the returned lifecycle plan violates the stated transition contract.
A callback context reset token is consumed from the wrong context · case 03
A callback context reset token is consumed from the wrong context; the returned lifecycle plan violates the stated transition contract.
A callback context reset token is consumed from the wrong context · case 04
A callback context reset token is consumed from the wrong context; the returned lifecycle plan violates the stated transition contract.
A callback context reset token is consumed from the wrong context · case 05
A callback context reset token is consumed from the wrong context; the returned lifecycle plan violates the stated transition contract.
Context restoration overwrites locals that the callback never modified · case 01
Context restoration overwrites locals that the callback never modified; the returned lifecycle plan violates the stated transition contract.
Context restoration overwrites locals that the callback never modified · case 02
Context restoration overwrites locals that the callback never modified; the returned lifecycle plan violates the stated transition contract.
Context restoration overwrites locals that the callback never modified · case 03
Context restoration overwrites locals that the callback never modified; the returned lifecycle plan violates the stated transition contract.
Context restoration overwrites locals that the callback never modified · case 04
Context restoration overwrites locals that the callback never modified; the returned lifecycle plan violates the stated transition contract.
Context restoration overwrites locals that the callback never modified · case 05
Context restoration overwrites locals that the callback never modified; the returned lifecycle plan violates the stated transition contract.
Absent places are treated as aliases · case 01
Absent places are treated as aliases.
Absent places are treated as aliases · case 02
Absent places are treated as aliases.
Absent places are treated as aliases · case 03
Absent places are treated as aliases.
Absent places are treated as aliases · case 04
Absent places are treated as aliases.
Absent places are treated as aliases · case 05
Absent places are treated as aliases.
Different allocation roots become aliases when projection depths differ · case 01
Different allocation roots become aliases when projection depths differ.
Different allocation roots become aliases when projection depths differ · case 02
Different allocation roots become aliases when projection depths differ.
Different allocation roots become aliases when projection depths differ · case 03
Different allocation roots become aliases when projection depths differ.
Different allocation roots become aliases when projection depths differ · case 04
Different allocation roots become aliases when projection depths differ.
Different allocation roots become aliases when projection depths differ · case 05
Different allocation roots become aliases when projection depths differ.
A common field prefix suppresses later disjointness · case 01
A common field prefix suppresses later disjointness.
A common field prefix suppresses later disjointness · case 02
A common field prefix suppresses later disjointness.
A common field prefix suppresses later disjointness · case 03
A common field prefix suppresses later disjointness.
A common field prefix suppresses later disjointness · case 04
A common field prefix suppresses later disjointness.
A common field prefix suppresses later disjointness · case 05
A common field prefix suppresses later disjointness.
Union storage is classified as disjoint sibling fields · case 01
Union storage is classified as disjoint sibling fields.
Union storage is classified as disjoint sibling fields · case 02
Union storage is classified as disjoint sibling fields.
Union storage is classified as disjoint sibling fields · case 03
Union storage is classified as disjoint sibling fields.
Union storage is classified as disjoint sibling fields · case 04
Union storage is classified as disjoint sibling fields.
Union storage is classified as disjoint sibling fields · case 05
Union storage is classified as disjoint sibling fields.
Unresolved dereference provenance is treated as disjoint · case 01
Unresolved dereference provenance is treated as disjoint.
Unresolved dereference provenance is treated as disjoint · case 02
Unresolved dereference provenance is treated as disjoint.
Unresolved dereference provenance is treated as disjoint · case 03
Unresolved dereference provenance is treated as disjoint.
Unresolved dereference provenance is treated as disjoint · case 04
Unresolved dereference provenance is treated as disjoint.
Unresolved dereference provenance is treated as disjoint · case 05
Unresolved dereference provenance is treated as disjoint.
A symbolic left index loses possible overlap with a nonzero index · case 01
A symbolic left index loses possible overlap with a nonzero index.
A symbolic left index loses possible overlap with a nonzero index · case 02
A symbolic left index loses possible overlap with a nonzero index.
A symbolic left index loses possible overlap with a nonzero index · case 03
A symbolic left index loses possible overlap with a nonzero index.
A symbolic left index loses possible overlap with a nonzero index · case 04
A symbolic left index loses possible overlap with a nonzero index.
A symbolic left index loses possible overlap with a nonzero index · case 05
A symbolic left index loses possible overlap with a nonzero index.
A symbolic right index is omitted from alias symmetry · case 01
A symbolic right index is omitted from alias symmetry.
A symbolic right index is omitted from alias symmetry · case 02
A symbolic right index is omitted from alias symmetry.
A symbolic right index is omitted from alias symmetry · case 03
A symbolic right index is omitted from alias symmetry.
A symbolic right index is omitted from alias symmetry · case 04
A symbolic right index is omitted from alias symmetry.
A symbolic right index is omitted from alias symmetry · case 05
A symbolic right index is omitted from alias symmetry.
Different known array elements retain a false conflict · case 01
Different known array elements retain a false conflict.
Different known array elements retain a false conflict · case 02
Different known array elements retain a false conflict.
Different known array elements retain a false conflict · case 03
Different known array elements retain a false conflict.
Different known array elements retain a false conflict · case 04
Different known array elements retain a false conflict.
Different known array elements retain a false conflict · case 05
Different known array elements retain a false conflict.
Sibling named fields retain a false conflict · case 01
Sibling named fields retain a false conflict.
Sibling named fields retain a false conflict · case 02
Sibling named fields retain a false conflict.
Sibling named fields retain a false conflict · case 03
Sibling named fields retain a false conflict.
Sibling named fields retain a false conflict · case 04
Sibling named fields retain a false conflict.
Sibling named fields retain a false conflict · case 05
Sibling named fields retain a false conflict.
A whole aggregate loses its conflict with a borrowed subplace · case 01
A whole aggregate loses its conflict with a borrowed subplace.
A whole aggregate loses its conflict with a borrowed subplace · case 02
A whole aggregate loses its conflict with a borrowed subplace.
A whole aggregate loses its conflict with a borrowed subplace · case 03
A whole aggregate loses its conflict with a borrowed subplace.
A whole aggregate loses its conflict with a borrowed subplace · case 04
A whole aggregate loses its conflict with a borrowed subplace.
A whole aggregate loses its conflict with a borrowed subplace · case 05
A whole aggregate loses its conflict with a borrowed subplace.
Outlives substitutes cardinality for program-point containment · case 01
Outlives substitutes cardinality for program-point containment.
Outlives substitutes cardinality for program-point containment · case 02
Outlives substitutes cardinality for program-point containment.
Outlives substitutes cardinality for program-point containment · case 03
Outlives substitutes cardinality for program-point containment.
Outlives substitutes cardinality for program-point containment · case 04
Outlives substitutes cardinality for program-point containment.
Outlives substitutes cardinality for program-point containment · case 05
Outlives substitutes cardinality for program-point containment.
Common valid lifetime includes points valid for only one referent · case 01
Common valid lifetime includes points valid for only one referent.
Common valid lifetime includes points valid for only one referent · case 02
Common valid lifetime includes points valid for only one referent.
Common valid lifetime includes points valid for only one referent · case 03
Common valid lifetime includes points valid for only one referent.
Common valid lifetime includes points valid for only one referent · case 04
Common valid lifetime includes points valid for only one referent.
Common valid lifetime includes points valid for only one referent · case 05
Common valid lifetime includes points valid for only one referent.
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 ↗