Skip to content

Static oracle: the generated units run close to their wall-clock backstop; cut their cost #163

Open

Description

@KyleAMathews

What happens

The static oracle's generated units (fixed seed 20261105: generated and random seed: generated, in packages/oracles/oracle-gaps/gap-report-static-oracle.property.test.mjs) run close to their per-test wall-clock backstop on the CI runner:

What changed in #99

The backstop is now 240 s, under the coordinator's ruling of 2026-11-17. It is a wall-clock backstop that fails loudly. It decides no outcome and is not a run budget, so raising it relaxes no law. The cost itself remains.

What would close it

  • Cut the unit's cost without lowering its run budget (P12): find where the time goes (fixture writes, Vitest config loads, analysis), and cut real cost first.
  • Then bring the backstop back toward 120 s.

Owner: the oracle-gaps maintainers. The next PR that touches the static oracle's grammar picks it up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions