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
Problem: whenever an error occurs somewhere down in the Python code, the batch job hangs and does not abort. When I login onto the compute note I see that there is 100% CPU usage. Not sure if this is a feature of my local cluster (I ported the scripts to SLURM cluster Cartesius) or the postprocessing scripts themselves. However it is clearly sub-optimal because the jobs need to be manually aborted.
The text was updated successfully, but these errors were encountered:
lvankampenhout
changed the title
jobs do not abort when error occurred
batch jobs do not abort when error occurred
Nov 6, 2018
lvankampenhout
changed the title
batch jobs do not abort when error occurred
batch jobs do not abort when error occurs
Nov 6, 2018
Problem: whenever an error occurs somewhere down in the Python code, the batch job hangs and does not abort. When I login onto the compute note I see that there is 100% CPU usage. Not sure if this is a feature of my local cluster (I ported the scripts to SLURM cluster Cartesius) or the postprocessing scripts themselves. However it is clearly sub-optimal because the jobs need to be manually aborted.
The text was updated successfully, but these errors were encountered: