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
Did anyone else notice that queued, not running, jobs do not get killed by Ganga when sending a kill() to the job?
In my Dirac job monitoring, the job is still registered as 'Waiting'. I tried to explicitly execute the kill command myself via
execute("kill(808596518)")
but this does not seem to change anything (aside from returning me [808596518]). Is there another command that needs to be send to Dirac?
(note that I can kill the jobs fine one-by-one via the CLI with dirac-wms-job-kill)
The text was updated successfully, but these errors were encountered:
From the mattermost:
Did anyone else notice that queued, not running, jobs do not get killed by Ganga when sending a kill() to the job?
In my Dirac job monitoring, the job is still registered as 'Waiting'. I tried to explicitly execute the kill command myself via
but this does not seem to change anything (aside from returning me [808596518]). Is there another command that needs to be send to Dirac?
(note that I can kill the jobs fine one-by-one via the CLI with dirac-wms-job-kill)
The text was updated successfully, but these errors were encountered: