🤖 Update Mock Benchmark Results

[thomhurst]

Automated Mock Benchmark Update

This PR updates the mock benchmark documentation with the latest results from the Mock Benchmarks workflow.

Benchmarks Produced

Individual benchmark artifacts are available for download:

• mock-benchmark-MockCreation
• mock-benchmark-Setup
• mock-benchmark-Invocation
• mock-benchmark-Verification
• mock-benchmark-Callback
• mock-benchmark-CombinedWorkflow
• mock-benchmark-summary (aggregated overview)

Libraries Compared

Libraries are discovered dynamically from the benchmark output. See the generated summary.json for the full list.

Changes

• Updated mock benchmark data in docs/static/benchmarks/mocks/latest.json
• Regenerated mock benchmark documentation in docs/docs/benchmarks/mocks/
• Updated mock benchmark summary in docs/static/benchmarks/mocks/summary.json

Workflow Run

• Run ID: 31765248537
• Triggered: schedule

---

🤖 This PR was automatically created and will be merged automatically once CI checks pass.

Summary by CodeRabbit

• Documentation
  • Updated mock benchmark results and charts with measurements from the August 14, 2026 CI run.
  • Refreshed performance, allocation, error, and garbage-collection metrics across callback, invocation, setup, creation, workflow, and verification scenarios.
  • Updated benchmark timestamps and host architecture details for accuracy.
  • Refined the latest benchmark report and summary metadata.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 05dee45c-1899-49d2-8a06-f1b54e81822d

📥 Commits

Reviewing files that changed from the base of the PR and between 3324652 and 928f28b.

📒 Files selected for processing (15)

• docs/docs/benchmarks/mocks/Callback.md
• docs/docs/benchmarks/mocks/CombinedWorkflow.md
• docs/docs/benchmarks/mocks/Invocation.md
• docs/docs/benchmarks/mocks/MockCreation.md
• docs/docs/benchmarks/mocks/Setup.md
• docs/docs/benchmarks/mocks/Verification.md
• docs/docs/benchmarks/mocks/index.md
• docs/static/benchmarks/mocks/Callback.json
• docs/static/benchmarks/mocks/CombinedWorkflow.json
• docs/static/benchmarks/mocks/Invocation.json
• docs/static/benchmarks/mocks/MockCreation.json
• docs/static/benchmarks/mocks/Setup.json
• docs/static/benchmarks/mocks/Verification.json
• docs/static/benchmarks/mocks/latest.json
• docs/static/benchmarks/mocks/summary.json

---

📝 Walkthrough

Walkthrough

The pull request refreshes mock benchmark documentation and JSON snapshots with measurements from the 2026-08-14 CI run. It updates chart data, timestamps, host architecture metadata, and aggregate benchmark results.

Changes

Mock benchmark refresh

Layer / File(s)	Summary
Refresh benchmark documentation docs/docs/benchmarks/mocks/*.md, docs/docs/benchmarks/mocks/index.md	Updated benchmark measurements, Mermaid chart values, generation dates, timestamps, and the reported architecture.
Refresh category snapshots docs/static/benchmarks/mocks/{Callback,CombinedWorkflow,Invocation,MockCreation,Setup,Verification}.json	Replaced category-level performance, allocation, generation, host, and timestamp data with results from the newer run.
Update aggregate benchmark output docs/static/benchmarks/mocks/latest.json, docs/static/benchmarks/mocks/summary.json	Updated aggregate measurements and metadata while retaining six categories and 78 benchmarks.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• thomhurst/TUnit#6579: Refreshes the same mock benchmark documentation and JSON artifacts.
• thomhurst/TUnit#6599: Updates the same mock benchmark snapshots with newer CI measurements.
• thomhurst/TUnit#6603: Refreshes the same mock benchmark documentation and JSON snapshots.

Poem

I’m a rabbit with charts in my den,
New benchmark numbers arrive once again.
The timestamps hop forward in line,
The v3 host records each sign.
JSON and Markdown now agree—
Fresh CI data for all to see!

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch automated-mock-benchmarks-update

---

_{Comment @coderabbitai help to get the list of available commands.}

[greptile-apps]

Greptile Summary

This automated update refreshes the published mock benchmark results from the August 14 CI run.

• Updates six per-scenario JSON datasets and their generated Markdown tables and charts.
• Refreshes the aggregate latest.json and summary.json artifacts.
• Updates benchmark timestamps and the documented runtime architecture from x86-64-v4 to x86-64-v3.

Confidence Score: 5/5

The PR appears safe to merge because the generated benchmark documentation and data remain structurally consistent and no actionable defect was identified.

The update is limited to generated benchmark values and run metadata, and the checked per-scenario, aggregate, table, chart, timestamp, and environment data agree.

Important Files Changed

Filename	Overview
docs/static/benchmarks/mocks/latest.json	Refreshes the consolidated mock benchmark dataset consistently with the checked per-scenario artifacts.
docs/static/benchmarks/mocks/summary.json	Updates aggregate run metadata while preserving the generated category and library structure.
docs/docs/benchmarks/mocks/index.md	Refreshes the benchmark date and runtime architecture to match the new run.
docs/docs/benchmarks/mocks/Callback.md	Regenerates the callback tables and charts with values matching the corresponding JSON data.
docs/docs/benchmarks/mocks/Invocation.md	Regenerates invocation benchmark tables and charts without changing their documented structure.
docs/docs/benchmarks/mocks/Verification.md	Regenerates verification benchmark tables and charts for the latest run.

_{Reviews (1): Last reviewed commit: "chore: update mock benchmark results" | Re-trigger Greptile}

[claude]

Code review

No issues found. This PR is a fully automated benchmark-data update (regenerated JSON results and generated Markdown tables under docs/static/benchmarks/mocks/ and docs/docs/benchmarks/mocks/), with no hand-written source or logic changes. Nothing here warrants code review — the content is machine-generated from a scheduled CI benchmark run, and the PR has already been auto-merged.