-
Notifications
You must be signed in to change notification settings - Fork 50
Testing fo Benchmark trigger as GH comment #1099
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
base: master
Are you sure you want to change the base?
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1099 +/- ##
===========================================
- Coverage 97.97% 55.55% -42.42%
===========================================
Files 237 28 -209
Lines 41192 2727 -38465
===========================================
- Hits 40356 1515 -38841
- Misses 836 1212 +376 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
/benchmark |
Benchmark ResultsThis is just simple markdown, render this however you'd like
|
PennyLane BenchmarksBenchmarks Report for lightning.qubitWorkflowsInterpreted
Hardware and Software Specifications
|
PennyLane BenchmarksBenchmarks Report for lightning.qubitWorkflowsInterpreted
Hardware and Software Specifications
|
Benchmark ResultsThis is just simple markdown, render this however you'd like
|
PennyLane BenchmarksBenchmarks Report for lightning.qubitWorkflowsInterpreted
Hardware and Software Specifications
|
PennyLane BenchmarksBenchmarks Report for lightning.qubitWorkflowsInterpreted
Hardware and Software Specifications
|
|
/benchmark |
PennyLane BenchmarksBenchmarks Report for lightning.qubitWorkflowsInterpreted
Hardware and Software Specifications
|
|
/benchmark |
1 similar comment
|
/benchmark |
PennyLane BenchmarksBenchmarks Report for lightning.qubitWorkflowsInterpreted
Hardware and Software Specifications
|
Before submitting
Please complete the following checklist when submitting a PR:
All new features must include a unit test.
If you've fixed a bug or added code that should be tested, add a test to the
testsdirectory!All new functions and code must be clearly commented and documented.
If you do make documentation changes, make sure that the docs build and
render correctly by running
make docs.Ensure that the test suite passes, by running
make test.Add a new entry to the
.github/CHANGELOG.mdfile, summarizing thechange, and including a link back to the PR.
Ensure that code is properly formatted by running
make format.When all the above are checked, delete everything above the dashed
line and fill in the pull request template.
Context:
Description of the Change:
Benefits:
Possible Drawbacks:
Related GitHub Issues: