A gate that does not depend on its machine, on a runner of its own
Test / gate (push) Canceled after 0s

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).
This commit is contained in:
alexm committed 2026-11-13 06:13:28 -05:00
1 parent 401084bab3
commit b10a5c87a3
31 files changed
+427 -104

No files matched your search

+5
View File
@@ -18,6 +18,9 @@ Mojo 1.2.0, held to the real compiler on the machine as well as on godbolt.org,
- Mojo is built one stated way everywhere core builds it or asks godbolt to (the Compile button, the corpus, the library's references, `mojo-local`, `mojo-fuzz`, `mojo-run`): the arguments are `build.args` in the library's pin, before a program's own. `--target-cpu x86-64-v3` makes a listing the same whichever of godbolt's machines answers (one answered with AVX-512, which the model machine does not know); `--fp-mode contract=off` rounds every Float64 operation on its own, as both interpreters do, where Mojo's default fuses a multiply with an add. `BUILD_ARGS` carries them and `BUILD_LEVELS` is new. `mojo build` with no arguments targets the machine it runs on and may fuse (`docs/trust.md`).
- The Mojo syntax definition the pipeline writes states its license as Apache-2.0 (it said MIT), and `THIRD_PARTY.md` says that the engines and the lessons, which came from the course, are under this repository's copyright and license.
- `pixi run cli prove` has no time limit unless `--budget-ms` gives one, and `library-check` proves without one: their answers are the prover's counted budgets' alone, the same on every machine. The clock is the caller's (`provePseudo(parsed, { budgetMs })`, `Workspace.proofBudgetMs`); left out, it is the Prove tab's 3 seconds (`PROVE_BUDGET_MS`), as before.
- The pinned environment has a C compiler on Linux (`gcc` from conda-forge, with the C library it links against pinned to glibc 2.34, which Mojo's runtime needs): `mojo build` links with the C compiler it finds, so until now a build depended on the system's, and on a machine without one (CI's image) no Mojo program could be built. The C references and the C harness are built with it too. `mojo-local` reports a program that could not be linked as that, not as rejected by the compiler, and does not keep the answer.
### Added
- `pixi run mojo-local` builds every Mojo program core holds or generates on the pinned local compiler and holds the checker, the interpreter and the translator to it; `pixi run mojo-fuzz` does the same with generated programs.
@@ -30,6 +33,8 @@ Mojo 1.2.0, held to the real compiler on the machine as well as on godbolt.org,
### Fixed
- The gate no longer depends on the machine it runs on. It first ran on the server that deploys the site, a slow container image without a C compiler or ICU, where ten tests failed on correct code and no Mojo program could be built. The pinned Dafny starts without ICU (it is run with `DOTNET_SYSTEM_GLOBALIZATION_INVARIANT=1`), and `dafny-fetch` fails when the Dafny it fetched does not start (it printed an empty version and went on). A test's time limit is processor time at the machine's pace (`tests/helpers/pace.mjs`), and the tests that hold what the prover proves give it no time on the clock.
- The workflows run on a runner with the label `heavy`, not on the deploy server: the gate builds and runs some 300 Mojo programs. `docs/ci.md` says how to register one, and describes the runners as they are (the workflows' comments described a host-mode runner that was never what ran them).
- The translator writes Mojo the compiler accepts and that prints what the pseudo prints.
- The Mojo interpreter: a numeric literal beside a Float32 is a Float32; a float to a whole power is computed as the compiler computes it, and to any other power the interpreter declines; a list in brackets takes a List's element type.
- The prover: 18 rules that proved what a run breaks are closed, each with a regression program in the library.