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
I am testing the slurmR package on my school HPC. Everything works great using the Slurm_lapply with plan="none" then sbatch call to launch the job array. However - I get the following strange error when using Slurm_collect.
Warning: The call to -sacct- failed. This is probably due to not having slurm accounting up and running. For more information, checkout this discussion: https://github.com/USCbiostats/slurmR/issues29
Error in x$njobs : $ operator is invalid for atomic vectors`
The code I run is
library(slurmR)
ans <- Slurm_lapply(1:10, sqrt, plan="none")
sbatch(ans)
result <- Slurm_collect(ans)
I understand my cluster does not have slurm accounting enabled - but it seems the error is unrelated to the warning? However when I enter debug mode, the x object has a njobs attribute and does not throw an error when I retrieve it directly.
The text was updated successfully, but these errors were encountered:
I have the same error. When this error occurs, the jobs were still executed but the job object was not assigned, so I had to look into the tmp_path folder and manually read the job.rds file. Looking at the traceback (copied below), it appears to happen when the input for status() is just a job ID (a character string, an atomic vector), which is allowed by the current function definition. Can you update the function so that the atomic vector input can be handled properly?
I am testing the slurmR package on my school HPC. Everything works great using the
Slurm_lapply
withplan="none"
thensbatch
call to launch the job array. However - I get the following strange error when usingSlurm_collect
.The code I run is
I understand my cluster does not have slurm accounting enabled - but it seems the error is unrelated to the warning? However when I enter debug mode, the
x
object has anjobs
attribute and does not throw an error when I retrieve it directly.The text was updated successfully, but these errors were encountered: