[II] Test W4A8 QSRT rate compatibility - #149
voipmonitor wants to merge 1 commit into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe PR adds tests for ChangesQSRT weight planning validation
Estimated code review effort: 2 (Simple) | ~10 minutes Mergeability Score: ⚪ Minimal · up to This PR adds focused planner coverage without changing runtime behavior, and no actionable merge-blocking risk remains after normal checks and review. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Closing without merge. The mixed-rate W4A8 QSRT rejection remains implemented in |
Status
Purpose
Protect the W4A8 QSRT planning contract enforced by commit
33cbfc70033473f85cc378da44fd8feca9c85610. W4A8 kernels decode one compile-time rate for an entire payload, while the H308 atom profiles carry per-pair K3/K4 rate selectors that require W4A16 execution.Resulting behavior
The CPU planner tests require both mixed-rate H308 profiles to fail closed under
quant_mode="w4a8_mx". The tests also require the supported coupled-K2 uniform-rate profile to retain the source-native Trellis layout.Compatibility
This pull request changes tests only. Runtime behavior remains defined by commit
33cbfc70033473f85cc378da44fd8feca9c85610.Validation
git diff --check: passed.Summary by CodeRabbit
w4a8_mxweight planning.