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

+8
View File
@@ -21,6 +21,14 @@ mojo = "==1.2.0" # the compiler the corpus is pinned to (library/mojo/pin.json)
nodejs = ">=26.10.0,<26.11" # the build and tests; the quest processor needs >= 22.6
python = ">=3.14.7,<3.15" # the corpus pipeline and the Dafny pin (standard library only)
# A C compiler, as `cc` and `gcc`: the Mojo compiler has the C compiler it finds link every program, library-check
# builds the C references with it, and one test builds a C harness. CI's image has none (docs/ci.md). Mojo's runtime
# libraries need glibc 2.34, so the C library the compiler links against is pinned to that and not conda-forge's
# default, 2.28, against which no Mojo program links. On macOS the compiler is the system's.
[target.linux-64.dependencies]
gcc = ">=16.2.0,<16.3"
sysroot_linux-64 = ">=2.34,<2.35"
[tasks]
# --- build and test --------------------------------------------------------
install = { cmd = "npm install", inputs = ["package.json"], outputs = ["node_modules/.package-lock.json"], description = "Install TypeScript (the only npm dependency)" }