Developer Test Environment¶
The Linux environment the gate needs, and the commands that prove it before a build trusts it. This context owns the VM lifecycle, the probes that report what the guest actually is, and the refusal that stops a Linux-only test from being run on a macOS host where the code it exercises was never compiled.
Language¶
Linux VM: The colima guest the VM half of the gate runs in. It carries guest kernel 7.0 for Landlock ABI V8, the pinned Rust toolchain, and the three backend services. Avoid: container, docker, devbox, sandbox Subsystems: Developer Test Environment Files: scripts/ksp-vm.sh, scripts/ksp-vm-provision.sh Relates to: VM Guard (is required by), Service Probe (is reported by) History: - 2026-11-17 (014-policy-scoped-sharing): Term introduced.
VM Guard: The one check that decides whether a command may run in the VM. It refuses when the host is not Linux or when the VM is not running, and it names the command that starts it. There is no fallback path: a Linux-only target that runs on the host reports a defect that is not there. Avoid: precondition, sanity check, environment check Subsystems: Developer Test Environment Files: scripts/lib/vm-guard.sh Relates to: Linux VM (guards), Provisioning (is superseded by a started VM)
Provisioning:
The idempotent command that brings a VM to the documented shape: resources,
guest kernel, toolchain, C build dependencies and the services enabled at boot.
A second run reports every step as no change and exits zero; a run that fails
names the step and leaves no half-created VM.
Avoid: setup, bootstrap, install (each names one part of it)
Subsystems: Developer Test Environment
Files: scripts/ksp-vm-provision.sh
Relates to: Linux VM (provisions), Status Report (is verified by)
Status Report: What the environment can and cannot do right now, in five groups: VM state, guest kernel and Landlock ABI, toolchain versions, each service endpoint with its health, and free disk. A group it cannot read is reported as unknown, never as healthy. Avoid: health check, diagnostics, doctor Subsystems: Developer Test Environment Files: scripts/ksp-vm.sh Relates to: Service Probe (is composed of), Provisioning (verifies)
Service Probe:
One endpoint question — is Valkey answering, is RustFS listening, is Garage
listening — asked of the endpoint rather than of systemd. A unit that is
active is not a server that answers, and the gate needs the second fact.
Avoid: ping, health check
Subsystems: Developer Test Environment
Files: scripts/ksp-vm.sh
Relates to: Status Report (composes), Linux VM (runs them)
Relationships¶
- A VM Guard refusal precedes every Provisioning and every VM-run target
- A Status Report is a list of Service Probe answers plus the facts only the guest can report
- Provisioning is verified by a second run of itself and by a Status Report