Hi,
I have noticed in v4.4 on two different systems a number of instances where I seem to need to kill jobs twice. Meaning, I kill a job, the job status changes to killed, and then a few seconds later, it spontaneously restarts. Killing the job a second time seems to kill it permanently. Has anyone else encountered this? It hasn’t really caused a problem thus far, it just seems odd.
Cheers
Oli
Thanks for reporting @olibclarke. Please can you email us the tgz file created by the
cryosparcm snaplogs
and include in your email
- project and job UIDs for jobs where you encountered the issue
- a link to this forum topic
1 Like
Will do the next time I notice it, thanks Wolfram!
I have a similar problem where big jobs like motion correction or CTF estimation do not properly clear and I cannot rerun them because the job then complains that directory is not empty. I have to clear them several times and refresh the window.
@martinpacesa @olibclarke Thank you for reporting the problem. We recorded the issue.
1 Like