← Command reference · lean-pkg comparator · CLI overview
lean-pkg comparator host-check
can this host run the comparator; read-only.
Usage
lean-pkg comparator host-check [--routes] [common flags]
[common flags]: --json, --commit, --push, --no-commit, also accepted before the command name; see the CLI overview.
Arguments and flags
| Argument or flag | Description |
|---|---|
--routes |
per route (judge = lake comparator in bwrap, prepare = setup stages, transfer = build here, judge elsewhere) supported yes/no with the reason, executables (type -P), locale, open-file limits, CPUs, cgroup memory and a command line per supported route; read-only; exit 0 when any route is supported |
Details
| Form | What it does | Key flags |
|---|---|---|
comparator host-check |
read-only, needs no registry: can this host produce comparator receipts? One ok/warn/fail line each for kernel, landlock (ABI; below 4 is a warn), bwrap (user namespace), go, cargo, jq, git, lean, lake, python3, then one mechanism toolchain|legacy: ok|fail line each against that mechanism’s own requirements (toolchain: bwrap, lean, lake, python3; legacy: Landlock ABI 1 or later, go, cargo, git, jq, lean, lake), then a verdict naming only the usable mechanisms and saying that Palomar runs only toolchain; exit 0 when one is usable, else 1; see The comparator tier. --routes (run it inside the job’s image with the job’s binds and PATH, before sbatch): one route judge|prepare|transfer: yes|no (reason) line each with run: command lines when supported (judge = lake comparator in bwrap, never an unsandboxed route; prepare = lean-pkg receipt comparator --prepare; transfer = build here, judge on a host with judge: yes), then executables resolved like type -P (the Slurm template’s tools included), locale (a set locale that is not installed is a warn), open-file limits with the LEAN_NUM_THREADS=3 advice when tight, CPUs, cgroup memory limit; additive JSON routes_schema, routes[], executables, locale, limits, resources, advice[]; exit 0 when any route is supported; see Planning routes before sbatch |
[--routes] [--json] |
Exit codes
Exit 1 is also a negative answer here:
comparator host-check: this host cannot run the comparator
JSON output
Top-level keys of --json, as recorded in the golden contract (tests/golden/json-keys.json):
comparator-host-check(exit depends on the host):can,checks,env_warnings,mechanism_detail,mechanisms,ok,palomar,verdictcomparator-host-check-routes(exit depends on the host):advice,can,checks,env_warnings,executables,limits,locale,mechanism_detail,mechanisms,ok,palomar,resources,routes,routes_schema,verdict
Examples
Can this machine produce comparator receipts? Needs no registry; exit 1 when it cannot.
lean-pkg comparator host-check
Per route (judge here, prepare here, build here and judge elsewhere), whether it is supported and why.
lean-pkg comparator host-check --routes