-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TORQUE trouble #12
Comments
This might be better suited for https://github.com/mllg/batchtools/ - to find out, do observer the same if your run it in pure batchtools (without the future framework), see my minimalistic code in #11 (comment) for an example - with the obvious tweaks to run TORQUE. |
All went smoothly, and I figured out that it was the configuration file. I had modified it, and I reverted to yours. I am still having trouble with the drake example, though: as I explain here, all the jobs hang in the Should I migrate this thread to |
If you can reproduce using batchtools alone, then yes migrate there. (future.batchtools is just a "futurizing" wrapper for batchtools.) |
Closing in favor of #12. This is not a problem with |
I am having a problem similar to #11 with TORQUE (on Ubuntu 16.04). I also posted on Stack Overflow. A
test.pbs
script seems to work just fine.But my jobs hang for
future_lapply()
viafuture.batchtools
.With
torque.tmpl
:My qstat shows
And
tracejob -n2 65
:and
qstat -f
:The text was updated successfully, but these errors were encountered: