Inputs cut short by the clock count only where a claim is open
Test / gate (push) Canceled after 0s

A proof report named a routine as stopped by the clock whenever the
generated inputs that cross-check it were cut short, even when every
claim of it was proved and nothing was left undecided. On a loaded
machine that is the common case: a container running the site's tests
on two processors reported it for the simplest proved example. The
prover running out of time still counts always; the inputs' clock
counts when a claim of the routine is still open.
This commit is contained in:
alexm committed 2026-11-13 07:32:45 -05:00
1 parent 38e6e2cdd2
commit 941af6bc78
5 files changed
+30 -9

No files matched your search

+1 -1
View File
@@ -23,7 +23,7 @@ Mojo 1.2.0, held to the real compiler on the machine as well as on godbolt.org,
### Added
- A proof report says when the time on the clock, not the proof, stopped a routine: `ProofReport.clock` has the budget and the routines it stopped, each such unit has `timedOut` and a note, and `checkProperties` answers `timedOut` when the clock cut its inputs short. The site uses it to offer more time.
- A proof report says when the time on the clock, not the proof, stopped a routine: `ProofReport.clock` has the budget and the routines it stopped, each such unit has `timedOut` and a note, and `checkProperties` answers `timedOut` when the clock cut its inputs short. Inputs cut short count only where a claim of the routine is still open: on a routine whose every claim is proved nothing was left undecided. The site uses it to offer more time.
- `pixi run mojo-local` builds every Mojo program core holds or generates on the pinned local compiler and holds the checker, the interpreter and the translator to it; `pixi run mojo-fuzz` does the same with generated programs.
- `pixi run mojo-fuzz --statements` generates whole programs (loops, branches, collections, records, routines with BYREF), builds each with the pinned compiler and holds its output to the pseudo's line by line; `pixi run prove-fuzz` holds the prover to runs of generated programs. `pixi run ci` runs both on a fixed and a moving seed, and `pixi run nightly` runs them longer.
- The Mojo interpreter runs what the translator writes: typed list literals, `List[T](slice)`, `ord` and `chr`, std.math's exact functions (`gcd`, `lcm`, `comb`, `hypot`, `fma`, `nextafter`, `ulp`, `copysign`, `isinf` and the others), `atof` of a decimal, and the `match` statement. What it declines on purpose (a fractional power, the transcendental functions, random numbers) says why.