search

christopherwharrop / rocoto

Rocoto Workflow Management System
Apache License 2.0
21 stars 16 forks source link

`@jobacct_duration` is always 0 resulting in extra calls to sacct if rocotorun has not been called in five days #42

Closed samtrahan closed 5 years ago

samtrahan commented 5 years ago

In samtrahan's updates to the slurmbatchsystem.rb, the @jobacct_duration variable is always 0. This means the sacct will be called twice for each job that cannot be found in a five day sacct history. Rocoto will still work, but the rocotorun may be slightly slow if someone turns on their CRONs after a week of downtime.

samtrahan commented 5 years ago

This is confirmed to be fixed in the bugfix/sacct-multi-day branch.

samtrahan commented 5 years ago

fixed in release/1.3.0