Adds automatic display of bechmark results #90
+34
−0
There are no files selected for viewing
This file contains 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,28 @@ | ||
| name: Run benchmarks | ||
|
|
||
| on: | ||
| pull_request: | ||
| types: [labeled, opened, synchronize, reopened] | ||
|
|
||
| # Only trigger the benchmark job when you add `run benchmark` label to the PR | ||
| jobs: | ||
| Benchmark: | ||
| runs-on: ubuntu-latest | ||
| if: contains(github.event.pull_request.labels.*.name, 'run benchmark') | ||
| steps: | ||
| - uses: actions/checkout@v2 | ||
| - uses: julia-actions/setup-julia@latest | ||
| with: | ||
| version: 1.4 | ||
| - name: Install dependencies | ||
| run: julia -e 'using Pkg; pkg"add PkgBenchmark BenchmarkCI@0.1"' | ||
| - name: Run benchmarks | ||
| run: julia -e 'using BenchmarkCI; BenchmarkCI.judge()' | ||
| - name: Post results | ||
| run: julia -e 'using BenchmarkCI; BenchmarkCI.postjudge()' | ||
| env: | ||
| GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||
| - name: Push results | ||
| run: julia -e "using BenchmarkCI; BenchmarkCI.pushresult()" | ||
| env: | ||
| GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||
This file contains 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -4,3 +4,5 @@ | |
| .DS_Store | ||
| docs/build/ | ||
| docs/site/ | ||
| /.benchmarkci | ||
| /benchmark/*.json | ||
|
Comment on lines
+7
to
+8
There was a problem hiding this comment. Are these files appearing? How are they generated? There was a problem hiding this comment. Locally these files appear for me. |
||
This file contains 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,4 @@ | ||
| [deps] | ||
| BenchmarkTools = "6e4b80f9-dd63-53aa-95a3-0cdb28fa8baf" | ||
| PkgBenchmark = "32113eaa-f34f-5b0d-bd6c-c81e245fc73d" | ||
| TaylorModels = "314ce334-5f6e-57ae-acf6-00b6e903104a" |
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you show/describe how this works? It seems to me from these lines that you need to add
run benchmarksomewhere to see this working.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
BenchmarkCI crates
Benchmark-resultbranch and saves results there.For example look at this PR, github-actions bot comments the results there, and saves them in
Benchmark-resultbranch here (In this repositories case we need not mentionrun benchmarkexplicitly)There are many ways one can trigger Benchmarking. In our case when some one adds
run benchmarklabel to the comment of PR. We can also have configuration that trigger benchmarking for each PR without mentioning it explicitly.