fix(ci): run the build-bearing nightly jobs on the box's light pool (#11965) - #11967
Merged
diegosouzapw merged 1 commit intoAug 29, 2026
Merged
Conversation
…11965) Four nightly jobs run a backend-only `next build` on ubuntu-latest (7 GB): Schemathesis, promptfoo injection guard, garak probes and the axe a11y suite (self-building webServer). On release/v3.8.51 three of them died with the hosted VM shutdown signature and nobody saw it — nightlies have no audience — and the fourth passes by a margin of minutes. They now target [self-hosted, omni-light] (hosted fallback when USE_VPS_RUNNER is off), a new two-listener label on the .113 box for jobs that need ~6 GB, not the 14-16 GB of a full build; they run once a day in the 04:00-06:00 UTC window, when the box is idle. Fleet reshaped the same day and documented in docs/ops/RUNNER_BOX.md: 4 active OmniRoute listeners (omniroute-113-5/-6 omni-build, omniroute-113/-2 omni-light), omniroute-113-3/-4/-7/-8 disabled (systemctl enable --now brings one back), janitor ceiling MAX_ACTIVE_RUNNERS=4. The remaining headroom limit is the VM's 31 GB of RAM (2 heavy + 2 light ≈ 42 GB peak, inside the 16 GB swap); more RAM on the Proxmox VM is the lever that turns the label ceilings into 3 heavy + 2 light. check:workflows --ratchet unchanged (194/194); check-workflows and backend-only-smoke-workflows suites pass; docs-sync PASS.
muhamadgalihsaputra
pushed a commit
to niyatna/NiyatnaRoute
that referenced
this pull request
Sep 27, 2026
…iegosouzapw#11965) (diegosouzapw#11967) Four nightly jobs run a backend-only `next build` on ubuntu-latest (7 GB): Schemathesis, promptfoo injection guard, garak probes and the axe a11y suite (self-building webServer). On release/v3.8.51 three of them died with the hosted VM shutdown signature and nobody saw it — nightlies have no audience — and the fourth passes by a margin of minutes. They now target [self-hosted, omni-light] (hosted fallback when USE_VPS_RUNNER is off), a new two-listener label on the .113 box for jobs that need ~6 GB, not the 14-16 GB of a full build; they run once a day in the 04:00-06:00 UTC window, when the box is idle. Fleet reshaped the same day and documented in docs/ops/RUNNER_BOX.md: 4 active OmniRoute listeners (omniroute-113-5/-6 omni-build, omniroute-113/-2 omni-light), omniroute-113-3/-4/-7/-8 disabled (systemctl enable --now brings one back), janitor ceiling MAX_ACTIVE_RUNNERS=4. The remaining headroom limit is the VM's 31 GB of RAM (2 heavy + 2 light ≈ 42 GB peak, inside the 16 GB swap); more RAM on the Proxmox VM is the lever that turns the label ceilings into 3 heavy + 2 light. check:workflows --ratchet unchanged (194/194); check-workflows and backend-only-smoke-workflows suites pass; docs-sync PASS.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
O que muda
nightly-schemathesis→ Schemathesisubuntu-latest(passa por minutos)[self-hosted, omni-light]nightly-llm-security→ promptfoo + garakubuntu-latest(2 jobs mortos em 28/08, sem step falho = VM derrubada)[self-hosted, omni-light]nightly-resilience→ axe a11y (webServer auto-builda o Next)ubuntu-latest(4/4 vermelho)[self-hosted, omni-light]Todos com fallback para hospedado quando
USE_VPS_RUNNERestá desligado (mesmo padrão donightly-release-green). Rodam 1×/dia entre 04:00 e 06:00 UTC, com a caixa ociosa.k6, heap-growth e chaos continuam hospedados (passam).Frota (feito hoje, reversível)
omni-lightemomniroute-113eomniroute-113-2(API, sem re-registro): jobs de ~6 GB.omniroute-113-3/-4/-7/-8desligados (systemctl disable --now;enable --nowtraz de volta) — só oBuilddamaine os nightlies usam a caixa, 8 listeners estavam ociosos e cada um é um inquilino potencial de 14 GB.MAX_ACTIVE_RUNNERS=4.Docs:
docs/ops/RUNNER_BOX.mdatualizado.check:workflows --ratchet194/194;check-workflows.test.ts32/32;backend-only-smoke-workflows.test.ts6/6;docs-syncPASS.Closes #11965