-
-
Notifications
You must be signed in to change notification settings - Fork 41
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
Add performance tests #384
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #384 +/- ##
=======================================
Coverage 87.91% 87.91%
=======================================
Files 62 62
Lines 10331 10331
=======================================
Hits 9083 9083
Misses 1248 1248 ☔ View full report in Codecov by Sentry. |
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.
Thanks @Amir-P for putting this in place
It looks good to me. I just have one or two comments
I have a general concern: Aren't these tests run on a virtual machine? If it is the case we might observe volatility on the result and possibly false negatives/positives?
Any thoughts on this?
.github/workflows/fleather.yml
Outdated
@@ -1,6 +1,10 @@ | |||
name: build | |||
|
|||
on: [push, pull_request] |
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.
I find it interesting to have the CI being run on a the branch before creating the pull request
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.
The reason for limiting push to master branch was the duplicated run of CI on PR but I think using push as trigger would solve it and enable running CI on every branch without PR too. I'll test it.
I talked to Alan outside of GitHub, and we decided to keep it as is but improve it in future for more streamlined local performance test run. We can also run on master and the current HEAD in the same virtual machine to have more realistic and stable performance tests (and maybe run multiple times and average the values). |
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.
Left a comment, let me know your thought
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.
LGTM
28de4e7
to
b34423f
Compare
b34423f
to
a3150a3
Compare
445ad7e
to
5662616
Compare
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.
Thanks for putting this in place
I have a tiny comment
No description provided.