A gate that does not depend on its machine, on a runner of its own
Test / gate (push) Canceled after 0s
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:
31 files changed
+427
-104
No files matched your search
@@ -25,7 +25,7 @@ What core holds:
|
||||
- verified routines (statistics, numerics, alignment, molecular simulation, sequences, special functions) that a program brings in with `USE`, each checked by every tool `pixi run library-check` has ([docs/library.md](docs/library.md));
|
||||
- the Mojo corpus (`library/mojo/`): the pin, material harvested from Modular's repositories at pinned commits, our own probes and programs, and godbolt's stored answer for every program we wrote and every harvested program that runs (the compiler's own diagnostic tests are asked only on request) ([docs/mojo-corpus.md](docs/mojo-corpus.md));
|
||||
- pseudo regression programs and the prover's soundness regressions (`library/pseudo/`).
|
||||
- **A command line:** `pixi run cli check|run|prove|fuzz|translate <file>` (`translate` takes `--to mojo`, `lingo`, `matho` or `speco`).
|
||||
- **A command line:** `pixi run cli check|run|prove|fuzz|translate <file>` (`translate` takes `--to mojo`, `lingo`, `matho` or `speco`; `prove` has no time limit unless `--budget-ms` gives one, so it says the same on every machine).
|
||||
|
||||
What core says about Mojo is pinned to **Mojo 1.2.0**. The checker and the interpreter are held to the real compiler's answers on the corpus: to godbolt's stored answers in the tests, and to the pinned compiler on a developer's machine with `pixi run mojo-local` and `mojo-fuzz`, which also build the Mojo the translator writes. On a program outside the corpus the interpreter can still run something the compiler rejects; [docs/trust.md](docs/trust.md) says what each verdict means and what it does not.
|
||||
|
||||
|
||||
Reference in new issue
Block a user