Enhancement: Only show benchmarks with significant changes in PRs
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- rust
- Domain
- ci-cd, performance
Research direction
Start by examining the canbench pull-request comment shown in the linked example and trace how benchmark results are selected for that CI comment. Define significant changes from the existing benchmark output, then verify that unchanged benchmarks are omitted while impacted benchmarks remain visible.
Written by the indexing model from the issue text.
Description
In a canbench PR comment like this one, we have many benchmarks, and it can be hard to spot which of the benchmarks exactly have been impacted. It'd be more readable if the CI comment only shows the specific benchmarks that have changed.
- Dominant language
- Rust
- Stars
- 21
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dfinity/canbench
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
All issues in dfinity/canbench
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gitbutlerapp/gitbutler#15998 · 1 comment ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100