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
Executing the following snippet leads to the exception Error: BatchtoolsExpiration: Future ('<none>') expired (registry path [..]). on our LSF powered cluster.
I am currently trying to resolve these issues for LSF and I do not think the three topics mentioned above apply.
This is because 1) I am spawning a very small number of jobs, 2) no error message was reported and 3) the LSF job status is set to DONE for jobs which expired:
[R script]
Error: BatchtoolsExpiration: Future ('<none>') expired (registry path [..]).. The last few lines of the logged output:
Sender: LSF System <[..]>
Subject: Job 212072182: <jobc6330b006f2ac3311db1511449421e23>in cluster <[..]> Done
Job <jobc6330b006f2ac3311db1511449421e23> was submitted from host <[..]> by user <[..]>in cluster <[..]> at Fri Apr 1 14:24:57 2022
[..]
$ bjobs 212072182
JOBID USER STAT QUEUE FROM_HOST EXEC_HOST JOB_NAME SUBMIT_TIME
212072182 [..] DONE gpu.4h [..] [..] *449421e23 Apr 1 14:24
I'd be excited to hear your thoughts on this. Did I do something wrong? Or is there a way of fixing this?
The text was updated successfully, but these errors were encountered:
Executing the following snippet leads to the exception
Error: BatchtoolsExpiration: Future ('<none>') expired (registry path [..]).
on our LSF powered cluster.with the following
lsf-simple.tmpl
:This topic has already been discussed in various settings:
Possible solutions have been suggested for SLURM (HenrikBengtsson/future.batchtools#74, #273).
I am currently trying to resolve these issues for LSF and I do not think the three topics mentioned above apply.
This is because 1) I am spawning a very small number of jobs, 2) no error message was reported and 3) the LSF job status is set to DONE for jobs which expired:
I'd be excited to hear your thoughts on this. Did I do something wrong? Or is there a way of fixing this?
The text was updated successfully, but these errors were encountered: