-
Notifications
You must be signed in to change notification settings - Fork 97
Track parsing in timing #2463
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?
Track parsing in timing #2463
Conversation
hannahbast
left a comment
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.
@Qup42 Quick feedback from 1-1 with Julian:
- Parsing time not reset to 0 for chained updates
- Time unaccounted for is now more than 0% again
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2463 +/- ##
==========================================
- Coverage 91.47% 91.09% -0.38%
==========================================
Files 463 465 +2
Lines 46955 39699 -7256
Branches 5242 5312 +70
==========================================
- Hits 42952 36165 -6787
+ Misses 2506 2024 -482
- Partials 1497 1510 +13 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
RobinTF
left a comment
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.
Just some minor suggestions
Overview
Conformance check passed ✅No test result changes. |
RobinTF
left a comment
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 time to parse an operation is now also tracked in the timing. Also fixed a bug in
resetofTimeTracer. The TimeTracer now is ashared_ptron the outer levels because we would have lifetime issues withTimeTracer&otherwise. (I assume that the process was similar for theCancellationHandle.)