The gate first ran on the server that deploys the site: a slow container
with no C compiler and no ICU. Ten tests failed there on correct code,
and no Mojo program could be built at all.
- The workflows ask for a runner labeled heavy, not the deploy server:
the gate builds and runs some 300 Mojo programs and fuzzes. docs/ci.md
says how to register one. With none registered a run waits.
- The pinned environment has a C compiler on Linux (gcc, with its C
library pinned to glibc 2.34): mojo build links with the C compiler it
finds, and conda-forge's default links against a C library too old
for Mojo's runtime. mojo-local reports a program that could not be
linked as that, and does not keep the answer.
- The pinned Dafny runs without ICU, and dafny-fetch fails when the
Dafny it fetched does not start.
- A test's time limit is processor time at the machine's pace
(tests/helpers/pace.mjs).
- The prover's time on the clock is the caller's: provePseudo and
Workspace.proofBudgetMs take it, the Prove tab's 3 seconds stay the
default, and the command line, library-check and the tests use none,
so their answers are the counted budgets' alone.
- The library pointer moves to its workflow change (e5ae090).