Skip to content
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

Serialise job (#19) #25

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Serialise job (#19) #25

wants to merge 3 commits into from

Conversation

uhager
Copy link
Contributor

@uhager uhager commented Mar 7, 2025

Renamed copy to clone to avoid clash with pydantic.BaseModel.copy. Fixed bug in threads_per_node.

Copy link

codecov bot commented Mar 7, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.66%. Comparing base (9f5fbc1) to head (88185ba).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #25      +/-   ##
==========================================
+ Coverage   81.38%   81.66%   +0.28%     
==========================================
  Files          54       54              
  Lines        3223     3267      +44     
==========================================
+ Hits         2623     2668      +45     
+ Misses        600      599       -1     

☔ 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
Collaborator

@reuterbal reuterbal left a comment

Choose a reason for hiding this comment

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

Very nice and mostly uncontroversial. A little suggestion to make/keep the API coherent, otherwise GTG from me.

@@ -48,52 +48,51 @@ def threads_per_node(self):
The number of logical cores per node (threads). This value is automatically derived
from the above properties.
"""
return self.cores_per_node * self.threads_per_core
return self.cores_per_node() * self.threads_per_core
Copy link
Collaborator

Choose a reason for hiding this comment

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

I think the API would be nicer if we declared cores_per_node (and for consistency) threads_per_node as properties. Then the look and feel of reading Job.threads_per_core and Job.threads_per_node is the same, even though one is derived from the other (which is an implementation detail that a user doesn't need to care about).

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