Test (in pplus-core) / in-core (push) Canceled after 0s
The gate builds and runs some 300 Mojo programs and fuzzes. The workflow now asks for the runner labeled heavy (pplus-core's docs/ci.md has its setup); with none registered a run waits. Its comments described a host-mode runner that was never what ran it.
2.9 KiB
2.9 KiB
Changelog
The format is based on Keep a Changelog. pplus-library has no version numbers: pplus-core pins it by commit, and each core release says which commit it holds.
[Unreleased]
Changed
- The Mojo corpus is harvested for Mojo 1.2.0 (it was 1.1.0), at the release tag of modular/modular and the matching commits of the other sources, with godbolt's answer for every program.
- Every Mojo program is built one stated way,
--target-cpu x86-64-v3 --fp-mode contract=off, written once inmojo/pin.json(build): a godbolt listing no longer depends on which of its machines answers, and floating-point arithmetic is rounded one operation at a time. Every stored answer was asked again under those arguments. - A routine's compiled references (Mojo and C) read their cases at run time, from standard input. Written as literals, the cases were worked out by the compiler while building, so its agreement was its constant folder's.
- Regression program 45 is
45-parallel-neighbor-race.pseudo, and the programs' own words are in US English. syntax/mojo.xmlstates its license as Apache-2.0 (it said MIT).- The workflow runs core's gate on the runner with the label
heavy, not on the server that deploys the site: the gate builds and runs some 300 Mojo programs.
Added
- Every routine's Mojo references have the pinned compiler's stored answer, and the probes record fourteen facts about Mojo 1.2.0 that core relies on, with two earlier questions corrected.
- 31 prover soundness regressions from an audit of the prover, and a regression program for the rules an audit of the interpreter pinned.
- Probes for what the translator's notes say about Mojo, for the Mojo the interpreter runs (typed list literals, slices,
ordandchr, std.math's exact functions,atof,match), for reading input on a pipe, and for the build arguments themselves;struct-field-loop-copyrecords a crash in code Mojo 1.2.0 builds. 55-statements.pseudo, the shapes the statement fuzzer found the translator getting wrong.- A workflow that checks the library on every push, by running pplus-core's gate against it.
THIRD_PARTY.md, every harvested file with its source and license header, andmojo/licenses/, each source's license file at the pinned commit.- The Apache License 2.0, a NOTICE, contributing rules, a security policy, a code of conduct, and a citation file.
2026-10-06
The state of main.
Added
- 16 verified routines in six modules (stats, numerics, align, md, seq, special), each written once in pseudo and checked at every level: cases, prover, fuzzer, generated Mojo, reference implementations in Python, C and Mojo, and a Dafny proof where one says something.
- The Mojo corpus, the probes, the exercise and stress programs, godbolt's answers, and the pseudo regression and prover soundness programs, moved here from pplus-core.