vm-tests: full-setup script lives in full-setup.py, build-time values in env, ruff in ci
This commit is contained in:
parent
8847fa48c9
commit
c1c5fe9704
1 changed files with 432 additions and 324 deletions
|
|
@ -124,6 +124,15 @@ root, through the real hive-priv unit), `hive-squid`, and `wg-hive` (two hives
|
|||
peered over the `wg-hive` mesh: handshake, traffic, and a wrong-key peer that
|
||||
must not handshake).
|
||||
|
||||
The `full-setup` script is plain Python in `nix/vm-tests/full-setup.py`, with no
|
||||
Nix interpolation. Commands the script runs in the VM find their binaries on the
|
||||
node's `environment.systemPackages`. Build-time values (socket path, forge
|
||||
domain, store paths) arrive as `FULL_SETUP_*` environment variables, set in
|
||||
`nix/vm-tests/full-setup.nix` through `overrideTestDerivation`. To add a value,
|
||||
set one there and read it with `os.environ` in the script. The `ruff (vm-tests)`
|
||||
job checks and format-checks `nix/vm-tests/*.py`; `nix/vm-tests/ruff.toml` names
|
||||
the globals the test driver provides.
|
||||
|
||||
## Configuration reference
|
||||
|
||||
`services.hyperhive.deploy.ci-runner.enable = true` on the host that runs it
|
||||
|
|
|
|||
Loading…
Reference in a new issue