-
Notifications
You must be signed in to change notification settings - Fork 615
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 benchmarks CI #4741
Add benchmarks CI #4741
Conversation
…ts with code coverage
Hello. You may have forgotten to update the changelog!
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #4741 +/- ##
==========================================
- Coverage 99.65% 99.64% -0.01%
==========================================
Files 383 383
Lines 34523 34263 -260
==========================================
- Hits 34403 34142 -261
- Misses 120 121 +1 ☔ View full report in Codecov by Sentry. |
Co-authored-by: Rashid N H M <[email protected]>
Co-authored-by: Rashid N H M <[email protected]>
Co-authored-by: Rashid N H M <[email protected]>
Co-authored-by: Rashid N H M <[email protected]>
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.
looks good to me. I'll let Rashid give the final ok
Co-authored-by: Rashid N H M <[email protected]>
[sc-38767] |
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.
🚀
@trbromley and @mlxd, this PR is ready to merge. Let me know if you have any thoughts on that. |
Context:
The PennyLane test suite currently hits almost all areas of the code base (~100% coverage). Since all areas of the codebase can be tested, these tests are in a good place to collect benchmarking data of the respective tested functions.
Description of the Change:
The CI was updated to include a new benchmarks pipeline hybridized through our tests pipeline.
The benchmarks CI will be triggered in a Pull request if the label
ci:run-benchmarks
is selected and on a schedule.The benchmark logs will be uploaded as artifacts, for further analyses.
Benefits:
Benchmark automation
Possible Drawbacks:
Related GitHub Issues: