From 2e9a65b4144d99a37cc1be829d78e2cd707c5b28 Mon Sep 17 00:00:00 2001 From: maia Date: Mon, 16 Nov 2026 20:35:58 +0100 Subject: [PATCH] docs: say how to run one VM test from the vm-nightly form, and the one-hour limit --- docs/4-implementation/scheduler/ci.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/4-implementation/scheduler/ci.md b/docs/4-implementation/scheduler/ci.md index 50ec7e341..592ce687f 100644 --- a/docs/4-implementation/scheduler/ci.md +++ b/docs/4-implementation/scheduler/ci.md @@ -125,8 +125,8 @@ one. checker resolves `test_driver`. [`.forgejo/workflows/vm-nightly.yml`](../../../.forgejo/workflows/vm-nightly.yml) builds all of them nightly at 02:30; a failing test fails that run. To run one by hand, start the workflow from the forge UI (Actions, vm-nightly, Run -workflow, optional `test` input), or run -`nix build .#vmTests.x86_64-linux.` on a host with KVM. Current tests: +workflow, then name one test in the `test` field), or run +`nix build .#vmTests.x86_64-linux.` on a host with KVM. An empty field builds all tests; together they can pass the runner's one-hour job limit, so name one test when you want one result. Current tests: `agent-ephemeral-rootfs` (the switch of an agent container to an ephemeral root, through the real hive-priv unit) and `hive-squid`.