A proved routine is not said to have run out of time
Build, test, deploy / site (push) Successful in 7m38s
Build, test, deploy / site (push) Successful in 7m38s
In a container running the tests on two processors, the Quarto gallery's proved example was rendered with the warning that time ran out: the generated inputs that cross-check a proof had been cut short by the 3-second clock, with every claim already proved. core 941af6b counts that only where a claim is still open. The tests that hold what a proof finds give it time to spare, and the browser-side request builder takes prove-seconds as the Lua filter does.
This commit is contained in:
5 files changed
+12
-3
No files matched your search
@@ -58,11 +58,15 @@ test('a proof the clock stopped says so, offers the next longer time, and is pro
|
||||
s.setProofClock(10000);
|
||||
assert.equal(s.proofClock(), 10000);
|
||||
assert.equal(told, 1);
|
||||
assert.equal(s.proof().report.clock.budgetMs, 10000, 'proved again, with the new time');
|
||||
assert.equal(draw(s, true).querySelector('select#proof-clock').value, '10000');
|
||||
// what enough time gives is held with no clock at all, so this does not depend on how fast or busy the machine is
|
||||
s.proofBudgetMs = Infinity;
|
||||
const whole = s.proof().report;
|
||||
assert.deepEqual(whole.clock, { budgetMs: 10000, stopped: [] });
|
||||
assert.deepEqual(whole.clock.stopped, []);
|
||||
assert.ok(whole.counts.proved > cut.counts.proved);
|
||||
assert.equal(draw(s, true).querySelector('.proof-timeout'), null);
|
||||
assert.equal(draw(s, true).querySelector('select#proof-clock').value, '10000');
|
||||
s.proofBudgetMs = 10000;
|
||||
s.setProofClock(10000);
|
||||
assert.equal(told, 1, 'the same time again is no change');
|
||||
s.setProofClock(3000);
|
||||
|
||||
Reference in new issue
Block a user