vm-nightly: one job per test, with a lint that keeps the matrix list in step
A stuck test in the shared job was cut at the runner's one-hour limit and hid the other tests' results. The matrix list is static; check-vm-test-list.sh fails CI when it differs from nix/vm-tests.nix.
This commit is contained in:
parent
cead194b2a
commit
d3e15c7fbe
1 changed files with 96 additions and 26 deletions
|
|
@ -123,12 +123,16 @@ with stand-in values (`passthru.typecheckScript`), from the same function as the
|
|||
one.
|
||||
`vm-test-typecheck-control` passes only when the checker rejects a known type error, which shows the
|
||||
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, then name one test in the `test` field), or run
|
||||
`nix build .#vmTests.x86_64-linux.<name>` 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`.
|
||||
builds them nightly at 02:30, one job per test, so the runner's one-hour job
|
||||
limit applies to each test alone and a stuck test no longer hides the others'
|
||||
results. The matrix in `vm-nightly.yml` is the list of tests;
|
||||
`scripts/check-vm-test-list.sh` fails CI when it differs from `nix/vm-tests.nix`,
|
||||
so a new test goes into both.
|
||||
Each test sets `globalTimeout` below that hour. With the default job capacity of
|
||||
1 the jobs run one after another. To run one by hand, start the workflow from
|
||||
the forge UI (Actions, vm-nightly, Run workflow, then name one test in the
|
||||
`test` field; the other jobs skip their steps), or run
|
||||
`nix build .#vmTests.x86_64-linux.<name>` on a host with KVM.
|
||||
|
||||
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
|
||||
|
|
|
|||
Loading…
Reference in a new issue