Repository navigation
make benchmark comments compact and show only the latest scan - #2178
Conversation
Refs ENG-6043; fixes #2160
Prime Agent performance — completedPR
Python runtime
Sandbox cost: ~$0.0882 — no inference calls. Methodology and samplesMain resolved at 2026-09-10T00:45:22.754612+00:00. Harness
|
Refs ENG-6043; fixes #2178.
Note
Low Risk
Changes affect benchmark comment formatting and internal report helpers only; no product runtime, auth, or data paths.
Overview
PR benchmark bot comments are narrowed to four columns (metric, main, PR, change) with delta and percentage in one cell, plus a single Overall count of regressed / improved / no clear change / incomplete / unavailable metrics instead of a legend and separate “Change %” and “Result” columns.
Significant moves get GitHub MathJax coloring: green
↓for improvements, red↑for regressions, with hue intensity scaling by relative change; noise-band deltas stay plain≈ ….comparison()now returns aComparisondataclass (outcome + formatted cells) instead of a five-tuple, and metricDefinitiondrops the oldbetter/worselabels.While status is
runningorpending-trust,render()omits tables and shows a short status line and run link so a new push can patch the same sticky comment with a running notice instead of leaving the previous scan visible until completion.Reviewed by Cursor Bugbot for commit ef100e2. Bugbot is set up for automated code reviews on this repo. Configure here.
Note
Make benchmark comments compact and show only the latest scan
Comparisonresult type with named outcomes (improved, regressed, no clear change, incomplete, unavailable) and signed delta-plus-percentage formatting with MathJax color intensity based on relative change.report.pycomparisonformatter returnsComparisonobjects instead of tuples; any out-of-tree consumers indexing the old tuple shape will break.Macroscope summarized ef100e2.