The GSM8K warm-cache investigation exposed several tiny-extend shapes where compute padding, valid-row selection, last-token collect, and all-gather rerange must stay request-slot aware. These tests pin those invariants without changing runtime behavior. Constraint: bs>1 tiny extends use page-granular compute slots while only a subset of rows are semantically valid Rejected: Rely on scalar non-padded token counts for these layouts | valid rows are not always a simple suffix mask Confidence: medium Scope-risk: narrow Directive: Do not weaken these tests unless the replacement path proves equivalent request-slot and valid-row semantics Tested: Remote pytest test_nsa_cp_utils.py as part of the 263-test CP regression suite Not-tested: CUDA graph paths; prefill does not use cuda graph in the current CP setup
Registered Tests
Tests under this directory are auto-discovered by run_suite.py via CI registration decorators.
Where Should I Put My New Test?
No server / engine launch required
| What you're testing | Directory | Requires |
|---|---|---|
| Component logic in isolation (cache, scheduler, config, parser, etc.) | unit/<module>/ |
CPU or GPU |
| CUDA kernel correctness | kernels/ |
GPU |
Server / engine launch required (E2E)
| What you're testing | Directory | Requires |
|---|---|---|
| Model inference correctness | models/, 4-gpu-models/, 8-gpu-models/ |
GPU |
| Feature-specific (OpenAI API, LoRA, speculative, distributed, VLM, etc.) | openai_server/, lora/, spec/, distributed/, ... |
GPU |
| Benchmarks (performance, accuracy, stress) | benchmark/ |
GPU |
| Platform-specific | amd/, ascend/ |
Vendor GPU |
See unit/README.md for unit test conventions.