You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I spindle srun, Slurm accounting captures two steps: spindle_be and spindle_bootstrap instead of the normal single entry that has the executable name. It would be nice if Spindle could use the -J option to the srun launcher to set the executable name as the job name.
The text was updated successfully, but these errors were encountered:
Thanks for the quick response! I'm not familiar with JSC. We are building the spank plugin but haven't enabled/tested it yet. Are there known issues? I saw #52 but don't fully understand the impact yet.
JSC = Juelich Supercomputing Center. They submitted the #52 PR.
The existing spank plugin kind of works, but isn't reliable enough to be used in production. There's a lot of corner cases where it fails. When I originally wrote it spank was missing a lot of capabilities that spindle wanted, and there's some very bad hacks in spindle's spank plugin to compensate. Since then slurm/spank has progressed, and #52 looks to clean a lot of that up.
The catch is that I lack a good test environment for slurm plugins, which I need before merging #52. I need to build one (probably through virtual cluster of slurm containers). But that's a big enough task that it's remained at the back of my queue behind El Capitan work for a while now.
When I
spindle srun
, Slurm accounting captures two steps:spindle_be
andspindle_bootstrap
instead of the normal single entry that has the executable name. It would be nice if Spindle could use the-J
option to the srun launcher to set the executable name as the job name.The text was updated successfully, but these errors were encountered: