Repository navigation
ci: expose compiler cache wall time and backend - #16230
Conversation
Co-authored-by: OpenAI <noreply@openai.com>
Report only an adopted seed distance so telemetry cannot claim a candidate seed after adoption fails. Co-authored-by: OpenAI <noreply@openai.com>
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configurationConfiguration used: Repository: manaflow-ai/cmux/.coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (2)
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: manaflow-ai/cmux/.coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (3)
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 7 remain after this review. 📝 WalkthroughWalkthroughThe CI workflow now passes seed distance only from the seed adoption step. Build metrics detect whether a scheme uses Fleet caching and include the aggregated cache backend and compile wall time in compiler-cache telemetry. ChangesCI build metrics
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Feature Merge Risk: ⚪ Minimal · up to This change adds cache backend and compile wall time to CI build telemetry and reports seed distance only when a seed is adopted. It affects CI metrics only, tests cover the new behavior, and no merge-blocking risk is identified. Security Architecture ReviewSecurity architecture risk: 🔵 Low · up to The change adds limited timing and cache metadata without changing the inspected security controls or exposing cache connection paths. Risk is low, with uncertainty about how the receiving host handles the expanded telemetry. Retained concerns Security review detailsSecurity Blast Radius
Security Findings and Attack Paths
Trust Boundaries and Controls
Resilience and Maintainability Implications
Hardening Proposals
🚥 Pre-merge checks | ✅ 24 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (24 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 8 functions across 2 files. (1 skipped: 1 unsupported.)
✨ Finishing Touches📝 Generate docstrings
🧪 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 |
|
All contributors have signed the CLA ✍️ ✅ |
CI failure attributionCI failed on
Matched log linesNot re-run automatically: Written by |
Bugbot is paused — on-demand spend limit reachedBugbot uses usage-based billing for this team and has hit its on-demand spend limit. A team admin can raise the spend limit in the Cursor dashboard, or wait for the next billing cycle to continue. |
|
Merge receipt for
Labeled |
Compiler-cache host telemetry currently reports Xcode task time but omits the actual compile wall time and whether the fleet CAS route was active. It also records a candidate seed distance when the candidate was not adopted. This PR adds bounded
compile_wall_secondsand categoricalcache_backend(localorfleet) to the host sidecar, and reports seed distance only from the adoption step that actually installed the seed.The backend is inferred from the Xcode build-settings echo and never copies the socket path into telemetry. Existing
compile_secondsremains the summed Xcode timing-summary task time;fetch_secondsremains seed DerivedData adoption/fetch duration.Validation:
7636d760e02:python3 tests/test_build_metrics.pyfailed with missing telemetry fields.623db13f882:python3 tests/test_build_metrics.py(9/9),python3 -m py_compile scripts/ci/build_metrics.py,bash tests/test_ci_fleet_compilation_cache.sh, andgit diff --checkpass.Changelog
Changed: expose compiler-cache wall time/backend and report only adopted seed distance in CI host telemetry.
Summary by cubic
Adds compiler-cache wall time and backend to CI host telemetry, and stops reporting seed distance when the candidate seed was never adopted.
compile_wall_secondsand categoricalcache_backend(localorfleet) in the host sidecar; the backend is inferred from Xcode build-settings and the socket path is never copied into telemetry.SEED_DISTANCEnow comes only from the step that actually installed the seed;compile_secondsremains the summed Xcode timing-summary task time andfetch_secondsremains the seed adoption/fetch duration.Written for commit 3c3a3ea. Summary will update on new commits.
Summary by CodeRabbit