You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fixes eng-6043: small measured deltas now receive muted red or green, with stronger colours for larger percentages.
preserves the noise threshold for arrows and overall assessments; exact zero and incomplete results remain neutral.
verified with 30 benchmark tests, repository checks, and github’s comment preview.
Note
Low Risk
Reporting-only change in the benchmark harness; noise thresholds and outcome aggregation are unchanged.
Overview
PR benchmark comments now show direction for small deltas while keeping the noise gate for arrows and headline counts.
In comparison, changes below the existing absolute/relative/spread threshold still count as no clear change and keep the ≈ prefix, but nonzero deltas are rendered with muted red or green MathJax text whose intensity scales with percentage. ↑/↓ and improved/regressed outcomes apply only when the delta exceeds the threshold; exact zero, incomplete, and unavailable rows stay uncolored.
The benchmarks README documents this split (color vs arrows vs summary). Tests cover sub-threshold coloring in full renders, colored small bundle deltas, and neutral exact-zero cells.
Reviewed by Cursor Bugbot for commit f69921c. Bugbot is set up for automated code reviews on this repo. Configure here.
Note
Color nonzero benchmark changes below the noise threshold in report.py
Updates the benchmark comparison helper in report.py so that nonzero complete changes are always passed through color rendering, regardless of whether they exceed the threshold. The threshold now controls only the displayed symbol (≈ vs directional arrow) and the outcome classification (no clear change vs regressed/improved). Exact-zero, incomplete, and unavailable comparisons remain uncolored. Tests in test_benchmarks.py and docs in README.md are updated to match.
Behavioral Change: within-threshold nonzero changes now render with direction-specific color markup where they were previously uncolored; exact-zero changes remain uncolored.
Main resolved at 2026-09-10T05:40:05.677813+00:00. Harness d4bc773d.
Linux x64, 4 vCPU, 8 GB RAM, 20 GB disk; region us.
Image: node:24-bookworm@sha256:be23f54a88d34e8824c741b19b91064094f92c1c97b194144bfc8b50d67258e2.
Stock tools, skills, daemon, and Python bootstrap enabled; fresh homes and a fixed Git fixture.
Onboarding is dismissed; the editor starts without a selected model or submitted prompt.
Medians shown. Arrows require a 20% timing/memory change plus absolute floors and IQR.
These practical noise floors are not a statistical significance test.
Cold means stopped Prime processes; OS filesystem caches are not flushed.
No model requests or credentials. Installation excludes build/setup time.
Installer tarballs use loopback; npm/Python downloads use the network with fresh caches.
Artifact size counts release tarballs; footprint after first use includes registry packages.
MB is decimal. Summed RSS can double-count shared pages; PSS is recorded when available.
Provisioning, setup, and build durations are recorded separately in the raw results.
Kernel probes use the installed JSONL runtime, outside the TUI/TypeScript host.
Per trial: 50 Python cells, 5 calls per shell case, and one 35-cell mix (9 git status calls).
Cell/shell values are batch means; other runtime timings are single operations.
State fixture: a 10,000-row × 8-column integer DataFrame and a 10,000-integer list.
Restore runs in a fresh kernel, including pandas imports; kernel startup is excluded.
Kernel RSS covers the isolated Python process; loaded RSS follows the pandas workload.
Costs estimate full sandbox lifetimes at configured rates, including setup and build.
Budget target: $1; not a billing cap. Checks are informational.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
Low Risk
Reporting-only change in the benchmark harness; noise thresholds and outcome aggregation are unchanged.
Overview
PR benchmark comments now show direction for small deltas while keeping the noise gate for arrows and headline counts.
In
comparison, changes below the existing absolute/relative/spread threshold still count as no clear change and keep the≈prefix, but nonzero deltas are rendered with muted red or green MathJax text whose intensity scales with percentage.↑/↓and improved/regressed outcomes apply only when the delta exceeds the threshold; exact zero, incomplete, and unavailable rows stay uncolored.The benchmarks README documents this split (color vs arrows vs summary). Tests cover sub-threshold coloring in full renders, colored small bundle deltas, and neutral exact-zero cells.
Reviewed by Cursor Bugbot for commit f69921c. Bugbot is set up for automated code reviews on this repo. Configure here.
Note
Color nonzero benchmark changes below the noise threshold in
report.pyUpdates the benchmark comparison helper in report.py so that nonzero complete changes are always passed through color rendering, regardless of whether they exceed the threshold. The threshold now controls only the displayed symbol (
≈vs directional arrow) and the outcome classification (no clear change vs regressed/improved). Exact-zero, incomplete, and unavailable comparisons remain uncolored. Tests in test_benchmarks.py and docs in README.md are updated to match.Macroscope summarized f69921c.