-
Notifications
You must be signed in to change notification settings - Fork 26
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
feat(minor): Add support for CI detection of absolute threshold improvements + signposts for Instruments #182
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #182 +/- ##
==========================================
- Coverage 71.70% 71.14% -0.56%
==========================================
Files 27 29 +2
Lines 3551 3652 +101
==========================================
+ Hits 2546 2598 +52
- Misses 1005 1054 +49
Continue to review full report in Codecov by Sentry.
|
Pull request benchmark comparison [ubuntu-latest] with 'main' run at 2023-09-13T18:03:26+00:00 |
## Description Delta for retain/release was misleading as initial retain count from alloc wasn't included, added new objectAllocCount metric. Other refactoring/cleanup. ## How Has This Been Tested? Manual testing + test suite. ## Minimal checklist: - [x] I have performed a self-review of my own code - [ ] I have added `DocC` code-level documentation for any public interfaces exported by the package - [ ] I have added unit and/or integration tests that prove my fix is effective or that my feature works
Co-authored-by: dimlio <122263440+dimlio@users.noreply.github.com>
Co-authored-by: dimlio <122263440+dimlio@users.noreply.github.com>
Description
Its desirable to be able to signal from CI if a threshold has been improved too and not only regressed, so we now return exit code 0 only for exact equal checks and 2 for regressions and 4 for improvements.
Added support for signposts (#183):
Added new objectAllocCount ARC stat counter and fixed the delta calculation to take initial refcount into account.
Also added support for returning setupState from the benchmark setup hooks, to allow access to state that can be reused per benchmark iteration.
How Has This Been Tested?
Manually tested + added unit test.
Minimal checklist:
DocC
code-level documentation for any public interfaces exported by the package