Name every Bencher workflow - #15
Merged
Merged
Conversation
Give each example workflow a top-level name that matches the GitHub Actions how-to, so runs are easy to tell apart in the Actions tab.
|
Bencher Report| Project | Example |
| Branch | workflow-names |
| Testbed | ubuntu-latest |
Click to view all benchmark results
| Benchmark | Latency | Benchmark Result nanoseconds (ns) (Result Δ%) | Upper Boundary nanoseconds (ns) (Limit %) |
|---|---|---|---|
| bencher::mock_0 | 📈 view plot 🚷 view threshold | 4.49 ns(-9.35%)Baseline: 4.95 ns | 11.26 ns (39.87%) |
| bencher::mock_1 | 📈 view plot 🚷 view threshold | 16.45 ns(+4.86%)Baseline: 15.69 ns | 22.22 ns (74.02%) |
| bencher::mock_2 | 📈 view plot 🚷 view threshold | 23.86 ns(-2.12%)Baseline: 24.38 ns | 31.05 ns (76.85%) |
| bencher::mock_3 | 📈 view plot 🚷 view threshold | 39.77 ns(+14.81%)Baseline: 34.64 ns | 42.22 ns (94.19%) |
| bencher::mock_4 | 📈 view plot 🚷 view threshold | 44.30 ns(-0.11%)Baseline: 44.35 ns | 50.90 ns (87.04%) |
|
| Project | Example |
| Branch | fork/workflow-names |
| Testbed | ubuntu-latest |
Click to view all benchmark results
| Benchmark | Latency | Benchmark Result nanoseconds (ns) (Result Δ%) | Upper Boundary nanoseconds (ns) (Limit %) |
|---|---|---|---|
| bencher::mock_0 | 📈 view plot 🚷 view threshold | 1.00 ns(-79.81%)Baseline: 4.95 ns | 11.26 ns (8.88%) |
|
| Project | Example |
| Branch | workflow-names |
| Testbed | Intel v1 |
⚠️ WARNING: No Threshold found!Without a Threshold, no Alerts will ever be generated.
Click here to create a new Threshold
For more information, see the Threshold documentation.
To only post results if a Threshold exists, set the--ci-only-thresholdsflag.
Click to view all benchmark results
| Benchmark | Latency | nanoseconds (ns) |
|---|---|---|
| bencher::mock_0 | 📈 view plot | 0.12 ns |
| bencher::mock_1 | 📈 view plot | 11.48 ns |
| bencher::mock_2 | 📈 view plot | 25.55 ns |
| bencher::mock_3 | 📈 view plot | 38.33 ns |
| bencher::mock_4 | 📈 view plot | 44.62 ns |
epompeii
marked this pull request as ready for review
October 1, 2026 23:26
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Every example workflow now carries a top-level
name:, matching the GitHub Actions how-to, so runs are easy to tell apart in the Actions tab and in the checks list on a pull request.name:base_benchmarks.ymlpr_benchmarks.ymlpr_benchmarks_closed.ymlfork_pr_benchmarks_closed.ymlpr_bare_metal_benchmarks.ymlpr_bare_metal_benchmarks_attach.ymlfork_pr_benchmarks_run.yml(Run Benchmarks) andfork_pr_benchmarks_track.yml(Track Benchmarks with Bencher) already had names and are unchanged, since the track workflow'sworkflow_runtrigger matches on the run workflow's name. Only the name line and a blank line are added; nothing else in the workflows changes.