Files
pplus-core/.gitea/workflows/test.yml
T
alexmandClaude 7ddc628597 Add USE and pin pplus-library: routines verified once, used by name
Routines that many programs need (a mean, a gap penalty, the
Lennard-Jones potential, the minimum image convention) were rewritten
and re-verified each time, and there was no way to open one and see
exactly what it does. They now live in pplus-library, pinned here as
the submodule library/, and a program brings them in with USE.

- USE module / USE module.Routine (pseudo-study resolveUses): each
  routine is studied once in its own file (its own USE lines resolved
  the same way, cycles refused) and handed to the checker as a library
  routine; unknown-library, unknown-routine, library-clash, use-place.
- A run steps over a library routine (one step at the call, one at the
  return, none of its lines); a broken contract is reported at the call,
  naming the routine. The prover uses its REQUIRE and ENSURE at the
  call and does not prove it again; it is not a unit of the program.
- pseudo-to-mojo writes each library routine the program calls once,
  dependencies first, labeled as coming from the library.
- src/library: the registry USE reads, generated from library/
  (scripts/library.mjs emit), so the site needs no files at run time.
- scripts/library.mjs check: every routine at every level: structure,
  cases, prover, fuzzer, generated Mojo, each reference implementation
  (CPython; cc at -O0 and -O2; core's Mojo interpreter; the pinned
  compiler's stored answer) held to the pseudo's results, and the Dafny
  proof with the pinned Dafny. Writes library/status.json and STATUS.md.
  scripts/library_godbolt.py stores the compiler's answers (network).
- pixi tasks library-check, library-emit, library-verify-mojo,
  library-harness; CI checks out the submodule and runs library-check.
- Tests: tests/library.test.mjs, corpus 53-library; docs/library.md and
  a library section in trust.md.

Gate: 332 pass; library-check: no failing check (16 routines; the Mojo
references are unverified until library-verify-mojo runs on the network).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FgvbRdoEheAHqsRmr2WuKZ
2026-10-05 12:06:41 +00:00

32 lines
1.2 KiB
YAML

# pplus-core on Gitea Actions, with a runner that has no container image: the act_runner runs jobs directly on the
# host's shell ("host mode"; pplus-web's docs/deploy.md has the runner setup). Every push and pull request builds
# and tests core, and checks that every Mojo program of ours still passes, offline, from godbolt's stored answers.
name: Test
on:
push:
pull_request:
workflow_dispatch:
jobs:
test:
runs-on: quarto-deploy
steps:
# library/ is pplus-library, a submodule; tests/library.test.mjs needs it checked out
- uses: actions/checkout@v4
with:
submodules: recursive
- name: Toolchain on the host
run: |
node --version
npm --version
python3 --version || echo "python3 missing: the pipelines' tests are skipped"
- run: npm ci
- run: npm test
- name: Our Mojo programs pass
run: |
if command -v python3 >/dev/null; then python3 scripts/mojo/corpus.py status --strict
else echo "python3 missing: corpus status skipped"; fi
# every library routine at every level the host has tools for (python3, cc); nothing may fail
- name: Library routines pass
run: node scripts/library.mjs check