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

fix(clean): make clean actually remove qwen36 and glm53, and pin it

JustVuggea94318482ff
diff --git a/c/tests/test_family_registry.py b/c/tests/test_family_registry.py
index 872cabea..b0498200 100644
--- a/c/tests/test_family_registry.py
+++ b/c/tests/test_family_registry.py
@@ -904,6 +904,7 @@ class FamilyRegistryTest(unittest.TestCase):
release = (repo / ".github" / "workflows" / "release.yml").read_text(
encoding="utf-8")
docker = (repo / "docker" / "Dockerfile.slim").read_text(encoding="utf-8")
+ clean = (repo / "c" / "tools" / "clean.py").read_text(encoding="utf-8")
make_rules = re.sub(r"\\\n[ \t]*", " ", makefile)
install_rule = re.search(r"(?m)^install:\s*(.*)$", make_rules)
self.assertIsNotNone(install_rule)
@@ -937,6 +938,16 @@ class FamilyRegistryTest(unittest.TestCase):
f"{family.id}: release.yml copies "
f"c/{family.engine_artifact} but never builds it")
self.assertIn(f"$(LIBEXECDIR)/{family.engine_artifact}", makefile)
+ # `make clean` must actually remove the engine. When it does
+ # not, a rebuild with different EXTRA_CFLAGS reports "up to
+ # date" and the caller silently keeps the OLD binary. The
+ # ASan step of the Qwen3.6 oracle job re-ran an
+ # un-instrumented qwen36 that way for as long as it existed
+ # (#1262): green, with the sanitizer never having run.
+ self.assertIn(f'"{family.engine_artifact}"', clean,
+ f"{family.id}: tools/clean.py does not remove "
+ f"c/{family.engine_artifact}, so a rebuild with "
+ f"different flags is a silent no-op")
else:
self.assertIn("deepseek-v4", ci)
self.assertIn("cp c/deepseek_v4", release)
diff --git a/c/tools/clean.py b/c/tools/clean.py
index 4a791003..560952e9 100644
--- a/c/tools/clean.py
+++ b/c/tools/clean.py
@@ -14,6 +14,14 @@ FILES = [
"inkling", "inkling.exe",
"kimi_k3", "kimi_k3.exe",
"olmoe", "olmoe.exe",
+ # Missing here means `make clean` leaves the binary in place, and a rebuild
+ # with different EXTRA_CFLAGS then reports "up to date". That is how the
+ # `Qwen3.6 tiny oracle` job re-ran an UN-INSTRUMENTED binary from its ASan
+ # step for as long as it existed (#1262), reporting green while the
+ # sanitizer had never run. test_family_registry keeps this list and the
+ # registry in step.
+ "qwen36", "qwen36.exe",
+ "glm53", "glm53.exe",
"glm", "glm.exe", # pre-rename name of the colibri engine
"iobench", "iobench.exe",
"backend_cuda.o", "backend_loader.o",