Repository navigation
test(cli): temporary full benchmark dry run (do not merge) - #7415
Prashansa-K wants to merge 18 commits into
Conversation
The benchmark comment holds a Lightweight Commands and an Integration Heavy Commands section. Each writer replaces only its own section, verifies it landed, and retries when another writer overwrote it. Previous runs record the result each section replaced. /bench full dispatches the stack benchmark workflow on the pull request's branch and refreshes the lightweight section only when it is behind the head commit. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ner counts The benchmark harness runs workloads that need a local stack: untimed setup and teardown shared per run or per block of launches, a stack switch, a runtime, fixtures, a shared native artifact cache, per-workload run counts, and tracing limits. Reports add container operation counts, a runtime column, a section name, shard packing, and a report merge. Every launch disables product telemetry. The stack manifest and fixtures are generated and committed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Runs from the Actions UI, the /bench full command, and a weekly schedule against the latest stable release. Plans shards, builds both binaries once, measures each shard on one runner, and reports to the job summary and the pull request comment. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… outputs Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Keep escaped table pipes through sanitizing, rebuild a comment another writer changed before writing it, keep each section's newest run and reallocate unused space when truncating, refresh a failed lightweight section on /bench full, skip launches when a setup step fails, and stage the migration fixture after setup for the migration workloads. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The lightweight and integration-heavy benchmarks each keep their own pull request comment, identified by its own hidden marker and carrying its own history and re-run note. This removes the shared-comment section markers, cross-section size budgeting and the read-back retry loop. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
CLI benchmark (Integration Heavy Commands): 5 things to checkCommit
API calls: none, before or after, for all 27 commands. Container operations: unchanged for all 17 commands. Binary size: 134.0 MB, unchanged. Details: timing ranges, API calls per command, container operations, slowest phasesTiming ranges
API calls per command
Container operations per command
Slowest phases
Comment |
CLI benchmark (Lightweight Commands): no changes foundCommit
API calls: unchanged for all 7 commands. Binary size: 134.0 MB, unchanged. Details: timing ranges, API calls per command, slowest phasesTiming ranges
API calls per command
Slowest phasesNo command moved beyond noise, so there are no phase deltas. Comment |
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Do not merge. This is a temporary test pull request for #7412 and will be closed without merging. It replaces #7413.
It adds one commit on top of
ci/cli-bench-stackthat makescli-bench-full.ymlalso run on a push to this branch, as if it were dispatched withworkloads: all,runtime: both, andbase: merge-base. This exercises the full benchmark end to end before merge, including its comments on this pull request. Dispatch,/bench full, and the schedule run only fromdevelop, so they are not covered here.🤖 Generated with Claude Code