Soiled dirty mud -> procset
The code is messy.
Using procset would simplify the code a lot, as interval sets are used almost everywhere, with many different types...
For example, look at batsim.py start_jobs* functions... :(
A GitLab upgrade is scheduled for Monday, May 12, 2025. The service will be unavailable for a few minutes in the morning. We'll keep you posted on the progress of the upgrade on the Mattermost channel: https://mattermost.inria.fr/devel/channels/gitlab. We recommend that you do not work on the platform until an announcement indicates that maintenance is complete.
The code is messy.
Using procset would simplify the code a lot, as interval sets are used almost everywhere, with many different types...
For example, look at batsim.py start_jobs* functions... :(
That would be great to unify the start_jobs_* and execute_jobs functions and document everything as well
FYI execute_jobs
is the maintained and up to date way to execute/start a job. Other versions are kept for simplicity and retro compatibility.
So am I allowed to remove every occurrence of the dirty start_jobs_* from batsim.py and the schedulers?
Yes let's clean this mud!
4-soiled-dirty-mud-procset
created branch 4-soiled-dirty-mud-procset
mentioned in merge request !4 (closed)
mentioned in merge request !5 (merged)
mentioned in commit 68d41ed6
closed via merge request !5 (merged)