Add PerLayerTransferContext: the per-request coordinator for overlapped per-layer KV transfer. submit_layer(layer_id, event) waits the layer's CUDA write event (on a background thread, never the compute stream) before async-submitting that layer's RDMA via the G1 path, so the transfer never reads a layer before its write kernel finished — the core correctness invariant for the forward overlap. finish() waits all accumulated batch_ids; idempotent per layer; fails closed. Unit-tested (test_cp_per_layer_transfer.py, 6 cases): event-wait-before-submit ordering, idempotency, empty-layer skip, finish-waits-all, submit-failure stop, wait-failure propagation. The scheduler/notifier wiring (A2-wiring + A3) builds on this. Co-Authored-By: Claude Opus 4.8 (1M context) <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.