Skip to content

122 sbatch#125

Merged
abhidg merged 4 commits intomainfrom
122-sbatch
Apr 15, 2025
Merged

122 sbatch#125
abhidg merged 4 commits intomainfrom
122-sbatch

Conversation

@abhidg
Copy link
Contributor

@abhidg abhidg commented Mar 4, 2025

@codecov
Copy link

codecov bot commented Mar 4, 2025

Codecov Report

Attention: Patch coverage is 82.85714% with 6 lines in your changes missing coverage. Please review.

Project coverage is 87.46%. Comparing base (d1678ae) to head (96c4aef).
Report is 5 commits behind head on main.

Files with missing lines Patch % Lines
cats/__init__.py 57.14% 6 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #125      +/-   ##
==========================================
+ Coverage   87.41%   87.46%   +0.04%     
==========================================
  Files          13       13              
  Lines         604      630      +26     
==========================================
+ Hits          528      551      +23     
- Misses         76       79       +3     

☔ 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

@andreww andreww left a comment

Choose a reason for hiding this comment

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

This all looks okay to me. Has it been tested in reality on a system running slurm?

@sadielbartholomew
Copy link
Member

@abhidg do you need a second review or is one sufficient?

@abhidg
Copy link
Contributor Author

abhidg commented Mar 10, 2025

@sadielbartholomew could you check if this PR works in a cluster? I don't have an account on our supercomputer ATM.

@sadielbartholomew
Copy link
Member

could you check if this PR works in a cluster? I don't have an account on our supercomputer ATM.

Sure, as long as you don't mind waiting a couple of days - I have some urgent work to sort for tomorrow and it will take a bit more time to review on JASMIN or ARCHER2. Will aim to submit a cluster-based review by the end of the week.

@colinsauze
Copy link
Member

I've just tested this on our cluster at NOC and it is happily submitting jobs to the slurm queue.
To match the behaviour of invoking sbatch directly (and how Cats works with At) it would be very helpful to be able to display the job number on screen after submission.

@colinsauze
Copy link
Member

Also tested on JASMIN (newer version of slurm, 24.11.0 instead of 23.02.6) and it is working there.

@abhidg
Copy link
Contributor Author

abhidg commented Apr 14, 2025

Thanks @colinsauze! I have created an issue to display the job number on submission.

@sadielbartholomew
Copy link
Member

Sorry @abhidg this clearly fell off my radar, but thanks @colinsauze for testing on JASMIN! Brilliant to hear that it is working with SLURM.

@abhidg abhidg merged commit 7c12384 into main Apr 15, 2025
9 checks passed
@andreww andreww deleted the 122-sbatch branch June 24, 2025 15:06
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.

scheduler: add sbatch

4 participants