Skip to content

Run frontier MoE models on hardware you already own — pure C, zero deps, experts streamed from disk. Tiny engine, immense model. 🐦

C

ci(olmoe): run the cap-budget test where the fixture already exists

JustVugg5d4454533bd7
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index 3adb160d..8aa63ba7 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -549,6 +549,14 @@ jobs:
SNAP=olmoe_tiny_c ./olmoe 8 8 olmoe_tiny/ref_olmoe.json | tee oracle.log
# the engine prints the score and exits 0 either way: the gate is here
grep -qE 'Matching tokens: ([0-9]+)/\1$' oracle.log
+ - name: "Cache cap: the sentinel takes the budget, an explicit cap is left alone"
+ run: |
+ cd c
+ # The cap used to be a constant 8 slots per layer whenever nobody
+ # chose one (#1443). It is now derived from the RAM budget, and the
+ # derivation needs a real container to size: this is the job that has
+ # one.
+ COLI_OLMOE_FIXTURE=olmoe_tiny_c python3 -m unittest -v tests.test_olmoe_cap_budget
- name: "Brain tab: HITS after every turn, on the grid EMAP declared"
run: |
cd c