3 Commits

Include renames

Author	SHA1	Message	Date
dc	f3d85d49bf	ci: make the memory check report its own input errors clearly ... A MIN_TOTAL_MB typo reached the integer test under set -e and aborted with "integer expression expected"; it now prints usage and exits 2. A kernel without MemAvailable no longer reports 0 MB available in the summary or the warning, so the oversubscription warning stays meaningful.	2026-11-01 18:06:28 +00:00
dc	b1892ebb98	ci: gate every job that builds the frontend, and scope the check in its header ... release.yaml (all three jobs), sites.yaml and release-assets.yaml run the same cold production build that the review jobs do, so they get the same pre-install check. The header now says what the check rules out (an undersized box) and what it does not (two jobs sharing one box), so the MemAvailable warning is not read as a gate.	2026-11-01 16:24:03 +00:00
dc	ab4f4c9b60	ci: fail a client job fast on a runner too small for it ... An undersized runner does not fail honestly: the kernel OOM killer takes the build, so the job reports exitcode 137 at ng build, or Karma disconnects mid-suite after twenty minutes. Both read as a flaky test rather than as a box that cannot hold the job, and both cost a whole CI slot. The check runs first in the three client jobs (Build-and-ng-test, Build-and-test-development, lighthouse), prints total and available RAM, vCPU count and any cgroup limit, and exits 1 when the effective size is under 8 GB - the supported minimum. A cold production build measures 3.8 GB peak on its own, so 8 GB leaves roughly 2x headroom.	2026-11-01 15:47:48 +00:00