Files
pplus-web/docs
alexm 3ebf2e2203
Build, test, deploy / site (push) Successful in 9m10s
A light deploy job, on a core whose gate does not depend on its machine
The deploy server is a slow container with other work to do. Its job ran
core's tests, which failed there (no C compiler, no ICU, limits written
for a fast machine), so nothing was published.

- pixi run ci, which the deploy job runs, is the site's tests and core's
  mojo-status-strict at the pinned commit. Core's own tests and
  everything that builds Mojo are core's gate, on a runner of its own;
  pixi run core-test stays for moving the pointer.
- The workflow and docs/deploy.md describe the runner as it is: a new
  container for every job, not a host shell.
- core moves to b10a5c8: a pinned C compiler for the Mojo compiler to
  link with, a Dafny that starts without ICU, time limits at the
  machine's pace, and a prover whose time on the clock is the caller's
  (the Prove tab keeps its 3 seconds).
2026-11-13 06:14:46 -05:00
..
2026-11-12 22:24:02 -05:00
2026-11-12 22:24:02 -05:00