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:
19 files changed
+240
-6
No files matched your search
@@ -50,6 +50,9 @@ for (const s of samples) for (const view of STATIC_VIEWS.filter((v) => v !== 'hw
|
||||
// the editor's token colors and the step colors, whichever a sample happened to show
|
||||
for (const c of ['tok-keyword', 'tok-builtin', 'tok-string', 'tok-number', 'tok-comment', 'tok-label', 'tok-op', 'tok-error', 'tok-punct', 'tok-convention', 'tok-transfer', 'tok-name']) used.add(c);
|
||||
|
||||
// the notice a rendered proof carries when the build machine ran out of the prover's time: no sample does (it is the machine's)
|
||||
used.add('proof-timeout');
|
||||
|
||||
/* ---------- styles.css as rules ---------- */
|
||||
|
||||
/** Top-level rules and @media blocks: { selector, body } or { media, rules }. Comments are dropped. */
|
||||
|
||||
Reference in new issue
Block a user