By: ValentinHirschi <valentin.hirschi@gmail.com>
apply CI resource overrides to the selected nextest profile Nextest resolves per-test overrides from the selected profile and default, so ci_gammaloop was bypassing the reservations stored under ci. Repeat the three existing resource/timeout policies in the selected profile, retaining plain-ci behavior and all local profiles, test selections and numerical inputs. Verified against the exact nextest 0.9.143 source used by CI, with independent review, parsed-config equivalence outside those overrides, config-version validation and diff checking. The preceding Linux run stopped after runner shutdown; this correction does not claim a passing test run or establish OOM. User prompt: Yes, continue as planned, it seems like it should be ok memory wise, so just let it run until LU scalar matrix is complete, and then really finalise the ALL_GREEN PR as mentioned earlier. Related user instruction: 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).
| Time to Start | Worker time | Duration | Time to finish | Idle | |
|---|---|---|---|---|---|
| Config | 2s | 4s | 4s | 7s | 2s |
| Eval | 9s | 46s | 46s | 55s | 2s |
| Build | 48s | 42m45s | - | - | 0s |
| Test | 2m37s | 10m54s | - | - | 0s |
| Deploy | - | - | - | - | 0s |
| Suite | 2s | 54m30s | - | - | 4s |