Repository navigation
ci(next): retain exact frame pacing receipts - #21314
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
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 |
|
Bead |
|
The feat-cmux-next push run https://github.com/manaflow-ai/cmux/actions/runs/39016200396 at 187858c failed: cmux app scheme compile (Debug), cmux-next fast tier. |
Frame-pacing currently surfaces warnings but leaves no durable, source-bound measurement artifact. This change writes a machine-readable
summary.jsonbeside the raw fling data, bound to the exact resolved source SHA and workflow SHA.The receipt records display status, per-mode median p50/p95 frame timings, dropped/total frames, thresholds, and regression annotations. Existing warning-only behavior is unchanged so unavailable GUI runners remain non-blocking while later ratchets have stable input.
Validation:
python3 tests/test_ci_frame_pacing_summary.pypython3 -m py_compile scripts/ci/frame-pacing/summarize.pypython3 tests/test_ci_frame_pacing_app_rpc.pygit diff --checkNeed help on this PR? Tag
@codesmith-botwith what you need.Summary by cubic
Writes a
summary.jsonreceipt beside the raw frame-pacing fling data, bound to the exact source and workflow SHAs that produced it.Written for commit a4337f1. Summary will update on new commits.