A gate that does not depend on its machine, on a runner of its own
Test / gate (push) Canceled after 0s
Test / gate (push) Canceled after 0s
The gate first ran on the server that deploys the site: a slow container with no C compiler and no ICU. Ten tests failed there on correct code, and no Mojo program could be built at all. - The workflows ask for a runner labeled heavy, not the deploy server: the gate builds and runs some 300 Mojo programs and fuzzes. docs/ci.md says how to register one. With none registered a run waits. - The pinned environment has a C compiler on Linux (gcc, with its C library pinned to glibc 2.34): mojo build links with the C compiler it finds, and conda-forge's default links against a C library too old for Mojo's runtime. mojo-local reports a program that could not be linked as that, and does not keep the answer. - The pinned Dafny runs without ICU, and dafny-fetch fails when the Dafny it fetched does not start. - A test's time limit is processor time at the machine's pace (tests/helpers/pace.mjs). - The prover's time on the clock is the caller's: provePseudo and Workspace.proofBudgetMs take it, the Prove tab's 3 seconds stay the default, and the command line, library-check and the tests use none, so their answers are the counted budgets' alone. - The library pointer moves to its workflow change (e5ae090).
This commit is contained in:
31 files changed
+427
-104
No files matched your search
@@ -2,34 +2,40 @@
|
||||
# mojo-status-strict (`pixi run nightly`). A failure opens nothing and sends nothing: the run goes red where anyone
|
||||
# looking at the repository's Actions page sees it. docs/ci.md says how to reproduce a seed and what to do with it.
|
||||
#
|
||||
# Gitea Actions (host mode) as test.yml; on GitHub Actions the same file runs with `runs-on: ubuntu-latest`.
|
||||
# Gitea Actions, on the `heavy` runner test.yml describes (never the deploy server); on GitHub Actions the same file
|
||||
# runs with `runs-on: ubuntu-latest`.
|
||||
name: Nightly
|
||||
on:
|
||||
schedule:
|
||||
- cron: "17 6 * * *" # 06:17 UTC, before the working day in America
|
||||
workflow_dispatch:
|
||||
|
||||
# one nightly run at a time: while no `heavy` runner is registered a run waits, and the next night's replaces it
|
||||
concurrency:
|
||||
group: nightly
|
||||
cancel-in-progress: true
|
||||
|
||||
env:
|
||||
CI: "true"
|
||||
PIXI_VERSION: "0.83.0"
|
||||
|
||||
jobs:
|
||||
fuzz:
|
||||
runs-on: quarto-deploy
|
||||
runs-on: heavy
|
||||
timeout-minutes: 90
|
||||
steps:
|
||||
- uses: actions/checkout@v4
|
||||
with:
|
||||
submodules: recursive
|
||||
|
||||
# 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 image'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
|
||||
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
|
||||
|
||||
Reference in new issue
Block a user