Reduce verbosity of execution benchmark results comment - #8868
Reduce verbosity of execution benchmark results comment#8868andrewlock wants to merge 6 commits into
Conversation
Execution-Time Benchmarks Report ⏱️Execution-time results for samples comparing This PR (8868) and master. ✅ No regressions detected |
BenchmarksBenchmark execution time: 2026-07-31 16:27:07 Comparing candidate commit 85c32ae in PR branch Found 0 performance improvements and 2 performance regressions! Performance is the same for 70 metrics, 0 unstable metrics, 69 known flaky benchmarks, 57 flaky benchmarks without significant changes.
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 329f524f3f
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
329f524 to
f3b30a4
Compare
f3b30a4 to
67b6105
Compare
67b6105 to
85c32ae
Compare
Summary of changes
Reduces the verbosity of execution benchmark results comment in GitHub
Reason for change
We did some while ago to make the github comments more compact, which improves the experience in the UI. However, in emails, where there's no dynamism to hide sections, the comments still leave giant responses, which is annoying.
Implementation details
Instead of including the whole report in the comment, only include a summary, and link out to the full results (which are uploaded as azure artifacts) instead. The markdown doc is then rendered in a custom app I forked and tweaked from here.
Test coverage
This is the test (once the comment is posted, click the link!)
Other details
I think we should take a similar approach for the benchmarking platform results, but will address that separately