Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #3 +/- ##
==========================================
+ Coverage 98.13% 98.82% +0.69%
==========================================
Files 5 6 +1
Lines 107 170 +63
==========================================
+ Hits 105 168 +63
Misses 2 2 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
micaeljtoliveira
left a comment
There was a problem hiding this comment.
@manodeep Looks good, but I have to admit I didn't look too closely at the regex stuff. The units tests seems to show it works as intended and that's good enough for me :)
I just have one small, optional, suggestion.
tests/test_um_parser.py
Outdated
|
|
||
|
|
||
| def test_um_metric_names(): | ||
| parser = UMProfilingParser() |
There was a problem hiding this comment.
The instantiation of the parser could be a module-level fixture.
There was a problem hiding this comment.
Yes, I didn't do it because it would make the test function calls quite long (mostly from my ridiculously long data fixture names), and then I am afraid to see what black would do to such long lines.
Still, I will give that parser-fixture a shot and see what the resulting code looks like
|
I am
|
|
@micaeljtoliveira I am done with my changes. Could not get the "ignore-columns-at-the-end" parsing feature to work - so I have left as is. |
|
@manodeep Just approved. Make sure you squash and merge or, alternatively, clean-up the git history before merging. |
|
@micaeljtoliveira Thanks! I cleaned up the commits - so should be good to go with a merge commit now. For reference, the GH UI would only let me squash+merge or rebase+merge if I clicked the "bypass branch protection" checkbox. |
|
I will merge once the CI passes fully. |
Ah, right, I must have disabled those in the branch protection rules. Sorry ;) |
Continuing on with this