Stuart Russell

This problem has been solved by the pull request [here](https://github.com/mllg/batchtools/pull/274#issue-662253912), though it may reveal another bug at `future.batchtools` as outlined [here](https://github.com/HenrikBengtsson/future.batchtools/issues/74#issue-912061418). After this bugfix I can run batchtools jobs on...

Hi @kpj I'm sorry I have no idea about LSF, but I was mistaken thinking that I needed `fs.latency = 60` - this hid the problem for a while, but...

> What kind of delay do you mean? In my case it was a provisioning delay, because the Slurm partition autoscaled down to 0 workers when not in use, so...

> I ended up running into the `BatchtoolsExpiration` Now you're *definitely* down the right track! (I hope...). I'd leave the NAs in, and try to work out how they're being...

> -q sets the queue for which to list jobs. How could that help in this case? Ah I misread the `-q` description - I'd understood it to list queued...

Sorry, `batchtools::makeClusterFunctionsSlurm` My apologies - it's very late/early here! Corrected in the original post too.

After submitting a pull request for a bugfix in `batchtools::waitForFile` [here](https://github.com/mllg/batchtools/pull/274#issue-662253912) the main issue mentioned above & [here](https://github.com/mllg/batchtools/issues/273#issue-903023047) has been solved, while leaving the `batchtools::makeClusterFunctionSlurm` scheduler.latency at 1, but I...

I had a terrible time trying to work this one out, but I summarised my problems & solutions [here](https://github.com/ropensci/targets/discussions/570#discussion-3475914). I didn't end up needing the proposed `fs.latency` trick - it...

The benchmark figures were just to make sure I'd chosen the right option. There real problem was a mismatch between `fn` passed to `batchtools::waitForFile` and the list of files to...

This seems to be caused by `future.batchtools` calling `batchtools::getStatus`, which defaults to 'expired' if `is.na(status)`. It doesn't affect `batchtools` as it's waiting for the log to appear in `waitForFile`. Here's...