-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run LSP benchmarks in CI #5546
Run LSP benchmarks in CI #5546
Conversation
The extra config in Cargo.toml is because of this issue: bheisler/criterion.rs#275 Once merged, this PR should be working: #5546
## Description The extra config in Cargo.toml is because of this issue: bheisler/criterion.rs#275 Once merged, this PR should be working: #5546 This doesn't affect running benchmarks locally. ## Checklist - [ ] I have linked to any relevant issues. - [ ] I have commented my code, particularly in hard-to-understand areas. - [ ] I have updated the documentation where relevant (API docs, the reference, and the Sway book). - [ ] I have added tests that prove my fix is effective or that my feature works. - [ ] I have added (or requested a maintainer to add) the necessary `Breaking*` or `New Feature` labels where relevant. - [ ] I have done my best to ensure that my PR adheres to [the Fuel Labs Code Review Standards](https://github.com/FuelLabs/rfcs/blob/master/text/code-standards/external-contributors.md). - [ ] I have requested a review from the relevant team or maintainers.
Benchmark for dbb86a5Click to view benchmark
|
Benchmark for ca37adeClick to view benchmark
|
Nice this will be handy. Just wondering if we should filter this job to run only if code in
|
Good call out. I realized that we also only want to run it on pull requests, not releases or pushes to master. I think it's cleanest as it's own workflow. What do you think? I also added all of the dependencies from sway-lsp's |
Benchmark for 2c186a1Click to view benchmark
|
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.
❤️
How does this chooses the commit to run? Last comment has Hovering the link it says |
Good catch, I would also expect the commits to be in the PR branch. It looks like the changes in the commit are correct, and the benchmark comparison is correct, so I think it's still worth using this. I've opened an issue: boa-dev/criterion-compare-action#115 |
Benchmark for 4bc8877Click to view benchmark
|
I agree with you that it seems to be working by the github action code. Have just approved this PR whilst we wait to see what the action author thinks of the modification. |
Benchmark for bb5d0adClick to view benchmark
|
Benchmark for 52d59c4Click to view benchmark
|
Description
Runs benchmarks in CI with criterion-compare-prs so the comparison shows as a comment on the PR.
The extra config in
Cargo.toml
is because of this issue: bheisler/criterion.rs#275. It needs to be merged to master first (#5547) for the benchmark comparison to work.Checklist
Breaking*
orNew Feature
labels where relevant.