minke.yu/sglang
1
0
Fork 0
Code Issues Pull Requests Actions 13 Packages Projects Releases Wiki Activity

[CI] Move the static ratchets back to CPU unit tests (#34913)

Browse Source
This commit is contained in:
Liangsheng Yin
2026-08-14 23:32:00 -07:00
committed by GitHub
parent 2a89c6823a
commit 5c9ee86d90
14 changed files with 399 additions and 371 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.claude/rules/unit-test-admission.md
+2 -3
View File
@@ -26,9 +26,8 @@ A new unit test case must fall into one of these categories:
3. **Critical-path bookkeeping.** Defends conventions that are easy to break by
forgetting to sync -- registry completeness, field lifecycle, serialization
compatibility. Enumerating assertions are fine here; the guarded failure
mode is "someone extended X without updating Y". Example: the namespace
coverage tests (`test/registered/unit/test_server_args_namespaces.py`). Static
source ratchets belong in `scripts/lint/` as checkers, not unit tests.
mode is "someone extended X without updating Y". Example: the ratchet tests
(`test/registered/unit/test_module_state_ratchet.py`).
Not admissible: