nevaforget/moonarch-pkgbuilds
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

ci(build): drop unverified OOM throttle, run cargo with -j2

Browse Source 
The previous CARGO_BUILD_JOBS=1 + nice + ionice throttling rested on an
assumed OOM diagnosis for run 86 (2026-04-23) that was never confirmed
via dmesg/journalctl. Build times tripled for no verified reason.
Remove the throttle; if a real OOM is captured in the future, re-add
limits with actual evidence.
This commit is contained in:
nevaforget 2026-04-24 09:05:46 +02:00
parent 5b6f35f480
commit 39b04d3829
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
.gitea/workflows/build-and-publish.yaml
View File

@ -53,14 +53,14 @@ jobs:
sudo pacman -S --needed --noconfirm $MAKEDEPS
fi
# Resource-constrained build. The act_runner shares CPU/RAM/I/O
# with the Gitea host (network-host mode). A parallel Rust build
# has OOM-killed the host: run 86 on 2026-04-23 stopped mid-compile
# with no error, taking gitea HTTPS down ~11 min. Force single-job
# compile and low CPU/IO priority so the host stays responsive.
export CARGO_BUILD_JOBS=1
export MAKEFLAGS="-j1"
nice -n 19 ionice -c 3 makepkg -sfd --noconfirm
# Parallel build with two cargo jobs. Previous single-threaded
# throttling was based on an unverified OOM assumption (run 86
# on 2026-04-23 stalled; no dmesg/journalctl evidence of
# OOMKiller was ever captured). If a real OOM happens, capture
# `dmesg | grep -i "killed process"` first before re-throttling.
export CARGO_BUILD_JOBS=2
export MAKEFLAGS="-j2"
makepkg -sfd --noconfirm
# makepkg can emit multiple artifacts per build (main + -debug
# split package). Upload each. Arch filename convention: