Skip to content

UM parser#3

Merged
manodeep merged 1 commit intomainfrom
um_parser
Sep 24, 2025
Merged

UM parser#3
manodeep merged 1 commit intomainfrom
um_parser

Conversation

@manodeep
Copy link
Collaborator

Continuing on with this

@codecov
Copy link

codecov bot commented Sep 23, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.82%. Comparing base (eb94c1f) to head (56aa56a).
⚠️ Report is 2 commits behind head on main.

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.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Member

@micaeljtoliveira micaeljtoliveira left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@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.



def test_um_metric_names():
parser = UMProfilingParser()
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The instantiation of the parser could be a module-level fixture.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@manodeep
Copy link
Collaborator Author

manodeep commented Sep 23, 2025

I am going to make this PR a draft - there are (edit: can't make the PR a draft since it's already approved, probably) make a couple of more things I would like to add:

  • missing function docstrings
  • Update regex to match all extraneous columns after matching the expected columns - i) this would make the code a bit more symmetric (arbitrary number of initial integer columns are ignored), and ii) potentially allow for parsing a bigger mix of UM versions

@manodeep
Copy link
Collaborator Author

@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.

@micaeljtoliveira
Copy link
Member

@manodeep Just approved. Make sure you squash and merge or, alternatively, clean-up the git history before merging.

@manodeep
Copy link
Collaborator Author

@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.

@manodeep
Copy link
Collaborator Author

I will merge once the CI passes fully.

@micaeljtoliveira
Copy link
Member

For reference, the GH UI would only let me squash+merge or rebase+merge if I clicked the "bypass branch protection" checkbox.

Ah, right, I must have disabled those in the branch protection rules. Sorry ;)

@manodeep manodeep merged commit 83206b5 into main Sep 24, 2025
8 checks passed
@manodeep manodeep deleted the um_parser branch September 24, 2025 04:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants