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
The current functionality for monitoring slurm jobs in a given flow run is by simply checking the output of squeue for the given user. However, if the user has other jobs running simultaneously, those will also get sucked in under this method and the flow will not complete until those unrelated jobs are no longer showing in squeue. One possible solution is to use the QC file to get the job IDs.
The text was updated successfully, but these errors were encountered:
The current functionality for monitoring slurm jobs in a given flow run is by simply checking the output of
squeue
for the given user. However, if the user has other jobs running simultaneously, those will also get sucked in under this method and the flow will not complete until those unrelated jobs are no longer showing in squeue. One possible solution is to use the QC file to get the job IDs.The text was updated successfully, but these errors were encountered: