The [HiCache-write]/[HiCache-load]/[HiCache-collective] and [CacheCtrl-write] per-operation logs fired at INFO on the scheduler thread during serving (every write-through, load-back, ack release, and rate-limited collective summary), eating into stream gaps. Demote all 29 to debug; one-time [HiCache-draft] init logs stay INFO and genuine failures stay WARNING (write_backup CP FAILED after deterministic retry). Also repair TestHiCacheEvictLoggingLevels, which asserted markers that no longer exist in this tree (stale list, failing on the pristine branch): pin the current hot-path markers as debug-only and extend the check to cache_controller. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.