Skip to content

Conversation

@iparask
Copy link
Collaborator

@iparask iparask commented Aug 29, 2025

This PR fixes the memory record in slurmise.

Closes #51

@iparask iparask requested review from biermanr and troycomi August 29, 2025 17:09
@coveralls
Copy link
Collaborator

coveralls commented Aug 29, 2025

Pull Request Test Coverage Report for Build 17414481295

Details

  • 13 of 13 (100.0%) changed or added relevant lines in 2 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.2%) to 92.959%

Totals Coverage Status
Change from base Build 17078564745: 0.2%
Covered Lines: 1500
Relevant Lines: 1611

💛 - Coveralls

Copy link
Collaborator

@troycomi troycomi left a comment

Choose a reason for hiding this comment

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

Looks reasonable. Is there a unit test for it?

@iparask
Copy link
Collaborator Author

iparask commented Sep 2, 2025

No, do you think we should add?

@iparask iparask merged commit ea9c401 into main Sep 2, 2025
4 checks passed
@iparask iparask deleted the gp/fix_memory branch September 2, 2025 21:14
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.

SLURM memory is not measured correctly.

4 participants