-
Notifications
You must be signed in to change notification settings - Fork 276
Refactor trace loop heads #5406
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
Conversation
18c3eed
to
f4a832e
Compare
Codecov Report
@@ Coverage Diff @@
## develop #5406 +/- ##
===========================================
- Coverage 68.19% 68.19% -0.01%
===========================================
Files 1176 1177 +1
Lines 97527 97531 +4
===========================================
+ Hits 66511 66512 +1
- Misses 31016 31019 +3
Continue to review full report at Codecov.
|
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.
To check: is there already regression test coverage?
// location of a sequence of same locations. | ||
// However, we don't want to suppress loop head locations because | ||
// they might come from different loop iterations. If we suppressed | ||
// them it would be impossible to know in which loop iteration |
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.
Typo "in which loop" -> "which loop"
The codecov reduction is because I made a file smaller, but the lines I removed were covered 😢 - the diff is 100% covered |
This models the logic for whether a trace step should be included away from whether the format is json or XML
f4a832e
to
f639b89
Compare
Refactoring of the common code for producing the location only steps. Feedback welcome. The goal here is to try and force the JSON and XML traces to be structurally the same