A proof's time limit is the reader's to set
Build, test, deploy / site (push) Successful in 7m44s

The Prove view gives each routine 3 seconds on the clock. On a slow or
busy device that runs out before the proof does, and claims stay open
with nothing to say why.

- The view says when the time, not the proof, stopped the checker, that
  what was not finished is open and not disproved, and offers to prove
  again with the next longer time. The setting is at the foot of the
  view: 3, 10 or 30 seconds or 2 minutes for each routine, kept in the
  browser (pplus.proveclock).
- A proof rendered with Quarto takes prove-seconds on the shortcode or
  pplus-prove-seconds for the site, and the render warns when the time
  ran out.
- The home page's own example is proved with no time on the clock, and
  the tests that hold a proof's outcome give it time to spare, so
  neither depends on the machine.
- core moves to 38e6e2c, whose report says which routines the clock
  stopped.
This commit is contained in:
alexm committed 2026-11-13 07:01:35 -05:00
1 parent d1955ad358
commit 7000662539
19 files changed
+240 -6

No files matched your search

+4 -1
View File
@@ -116,7 +116,10 @@ test('every rendered view draws for a program that has what it needs, with the a
assert.ok(r.markdown.length > 10, `${view} has a Markdown form`);
}
assert.match(renderStatic({ view: 'flow', files }).html, /<svg[^>]*class="flow-svg"/);
assert.match(renderStatic({ view: 'proof', files }).html, /4 proved/);
// with time to spare: the 3 seconds a rendered proof has by default can run out on a slow machine (prove-seconds)
const proof = renderStatic({ view: 'proof', files, proveSeconds: 600 });
assert.match(proof.html, /4 proved/);
assert.deepEqual(proof.warnings, []);
const check = renderStatic({ view: 'check', files: { pseudo: problemById('five-bugs').sources.pseudo } });
assert.match(check.html, /problem-error/);
assert.match(check.markdown, /\*\*error\*\*, pseudo line \d+: /);