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
@@ -27,6 +27,9 @@ test('the gallery\'s samples render as a page would get them, and every run in i
|
||||
const view = def.view ?? (s.attrs.view === 'dataflow' ? 'data' : s.attrs.view);
|
||||
const req = requestFor(view, s.attrs, files);
|
||||
if (def.hw) req.hw = [def.hw];
|
||||
// a proof with time to spare: the 3 seconds a page gets by default can run out on a loaded machine, and the
|
||||
// render then warns (prove-seconds); what the sample proves is held here, not how fast this machine is
|
||||
if (view === 'proof') req.proveSeconds = 600;
|
||||
const r = renderStatic(req);
|
||||
assert.deepEqual(r.warnings, [], `${s.name} ${JSON.stringify(s.attrs)}`);
|
||||
if (r.expect) assert.ok(r.expect.ok, `${s.name}: ${JSON.stringify(r.expect)}`);
|
||||
|
||||
Reference in new issue
Block a user