0ad34794

By: ValentinHirschi <valentin.hirschi@gmail.com>

bound exact CFF cache capacity and correct macOS memory guarding

Keep each exact-CFF request's normalized capacity in the cache key, preserving
its immutable numerator assignment and preventing independent terms from
forming an unnecessarily large Cartesian degree envelope. Measure the owned
process tree using native macOS physical footprint so compression and swap do
not evade the 30 GB guard. Reserve the existing large CI fixtures, correct the
JUnit path and Nextest minimum, and remove one unused Clippy lifetime binder.
Include the shared graph fixture directory in isolated Nix test build sources
so compile-time include_str! inputs are available to all three owning packages.

This remains a validation candidate, not ALL_GREEN. The complete scalar matrix,
fresh final focused/full gates and matching remote CI must still finish.

User prompt:
Ok continue as planned now, trying to finish this damn scalar LU matrix, and only looking for improvement to the code if you can find relatively non-invasive cheap wins. The core objective is getting to ALL_GREEN commit and push merge-ready state of the corresponding PR. Then stop yourself and deem the goal achieved (if there does not seem to be any gross oversight w.r.t what is in it).

Related user instruction:
I think the memory watchdog runner is not counting ram properly change it to follow just that process tree.
Also when rerunning can you start from GL16 directly?
GitHub
Time to Start Worker time Duration Time to finish Idle
Config 2s 14s 14s 16s 2s
Eval 13s 46s 46s 59s 0s
Build 52s 1h40m35s - - 17s
Test 2m28s 10m23s - - 0s
Deploy - - - - 0s
Suite 2s 1h51m59s - - 20s

Timeline

Config Eval Build Test Failed Retried Compressed gap
0s1m2m3m4m5m6m7m8m9m10m11m12m13m14m15m16m17m18m19m20m21m