You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 7e2b3d0
Browse filesBrowse the repository at this point in the historyBrowse files
A link holds a permit of the build's compiler limit, and a POSIX link is published by one command
Under bmi_schedule = "on" with GCC ninja runs six jobs per compiler and the
generation's semaphore bounded only the compilers, so every link a build
reached at once ran at once: mcpp's 26 test programs relinked together at 1
to 1.8 GB each and the 16 GB CI runner ran out of memory (unit-linux-archive,
on every commit of this branch). A link now takes a permit of the same
semaphore; the graph still names no number (e2e 861).
The permit's transaction judges its output when the held command exits, so
the permit wraps the whole publication: a POSIX link is published through a
temporary name by mcpp link-output --temporary rather than a shell sequence
whose rename followed the linker, which recovery took for an uncommitted
output and removed.
The tests are built by the pinned bootstrap, which predates this: ci-unit
builds the archive with bmi_schedule off for a bootstrap older than
2026.11.16.1, whose ordinary job count bounds links.
Measured from main's restored test build at MCPP_JOBS=4: the bootstrap ran
up to 7 links at once in 539 s, this engine at most 4 in 360 s.
0 commit comments