Compare commits

..
1 Commits
Author SHA1 Message Date
alexm e5ae0904cf 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.
2026-11-13 06:10:37 -05:00
2 changed files with 11 additions and 8 deletions

No files matched your search

+10 -8
View File
@@ -10,8 +10,10 @@
# default one. A red run can be core's own: look at core's latest run first. The repository variable CORE_REF, when
# set, names another ref of core to test against (a branch made for the same change).
#
# Gitea Actions (host mode, as pplus-core's workflows); on GitHub Actions the same file runs with
# `runs-on: ubuntu-latest`. core is read from the same owner on the same server as this repository.
# Gitea Actions, on the runner with the label `heavy`, as pplus-core's own gate (its docs/ci.md has the runner's
# setup): the gate builds and runs some 300 Mojo programs, so it never runs on the server that deploys the site, and
# with no `heavy` runner registered a run waits. On GitHub Actions the same file runs with `runs-on: ubuntu-latest`.
# core is read from the same owner on the same server as this repository.
name: Test (in pplus-core)
on:
push:
@@ -28,10 +30,10 @@ env:
jobs:
in-core:
# a pull request runs only from a branch of this repository: on a host runner a fork's workflow would run its
# own code on the droplet (docs/deploy.md in pplus-web). Drop this line for a runner that is a throwaway VM.
# a pull request runs only from a branch of this repository: a fork's workflow would run its own code on the
# runner (docs/ci.md in pplus-core). Drop this line for a runner that is a throwaway machine.
if: github.event_name != 'pull_request' || github.event.pull_request.head.repo.full_name == github.repository
runs-on: quarto-deploy
runs-on: heavy
timeout-minutes: 60
steps:
- name: pplus-core, its default branch (or CORE_REF)
@@ -45,15 +47,15 @@ jobs:
with:
path: core/library
# pixi: the host's when it is the pinned version, else the pinned release, fetched once into a cache directory
# the runner's user owns (no sudo), checked by SHA-256
# pixi: the runner's when it is the pinned version, else the pinned release, fetched into a cache directory
# (which lasts only where the runner keeps a home between jobs) and checked by SHA-256
- name: pixi, pinned
shell: bash
working-directory: core
run: |
set -euo pipefail
if command -v pixi >/dev/null && [ "$(pixi --version | cut -d' ' -f2)" = "$PIXI_VERSION" ]; then
echo "pixi $PIXI_VERSION is on the host: $(command -v pixi)"; exit 0
echo "pixi $PIXI_VERSION is on the PATH: $(command -v pixi)"; exit 0
fi
dir="${PPLUS_CI_CACHE:-$HOME/.cache/pplus-ci}/pixi-$PIXI_VERSION"
if [ ! -x "$dir/pixi" ]; then
+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