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
@@ -113,6 +113,7 @@ export function requestFor(view: StaticView, attrs: Record<string, string>, file
|
||||
if (attrs.t && Number.isFinite(Number(attrs.t))) req.t = Number(attrs.t);
|
||||
if (attrs.title) req.title = attrs.title;
|
||||
if (attrs.max && Number.isFinite(Number(attrs.max))) req.max = Number(attrs.max);
|
||||
if (Number(attrs['prove-seconds']) > 0) req.proveSeconds = Number(attrs['prove-seconds']);
|
||||
if (attrs.views) req.hw = list(attrs.views);
|
||||
if (attrs.preset) req.preset = attrs.preset;
|
||||
if (attrs.listing === '0') req.listing = false;
|
||||
|
||||
Reference in new issue
Block a user