CI: run core's gate on the heavy runner, not the deploy server
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.
This commit is contained in:
alexm committed 2026-11-13 06:10:37 -05:00
1 parent 568474d52f
commit e5ae0904cf
2 files changed
+11 -8

No files matched your search

+1
View File
@@ -12,6 +12,7 @@ pplus-library has no version numbers: pplus-core pins it by commit, and each cor
- 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.xml` states 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