-
Notifications
You must be signed in to change notification settings - Fork 48
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
remove Pkg.add from Benchmark #711
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #711 +/- ##
==========================================
+ Coverage 96.27% 96.33% +0.05%
==========================================
Files 34 34
Lines 3356 3356
==========================================
+ Hits 3231 3233 +2
+ Misses 125 123 -2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Benchmark Report for /home/runner/work/MixedModels.jl/MixedModels.jlJob Properties
ResultsA ratio greater than
Benchmark Group ListHere's a list of all the benchmark groups executed by this job:
Julia versioninfoTarget
Baseline
|
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 cleaning this up.
I feel that we should think about whether we want to continue to do package benchmarks. It seems that the results are so variable as not to be worthwhile.
For example, if you check out the main branch and run the package benchmark you are essentially benchmarking the main branch against itself and you frequently end up with "significant" differences.
I agree. I can disable this as CI and we can revisit this if we find a good set of benchmarks / thresholds so that we're not just seeing noise in GitHub's server farm. |
No description provided.