-
Notifications
You must be signed in to change notification settings - Fork 9
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
Issue running with Singularity on SLURM #33
Comments
Ok, so downgrading {targets} to 1.2.2 solved things for now and I can run my analysis. However, I see a number of changes in 1.3.0 which i suspect account for the error. I can run the targets-minimal pipeline without issue, but when i include the following to run it on SLURM, I get errors.
If I remove the
I get no error, but the pipeline never progresses beyond dispatching the first target:
Apologies if I'm missing something obvious, but are you able to provide any insight? |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Prework
crew.cluster
package itself and not a user error, known limitation, or issue from another package thatcrew.cluster
depends on.Description
After updating a slew of packages recently, my SLURM-enabled targets pipeline has stopped running, with errors about
seconds_timeout
. I have a rather elaborate script to setup cluster operations, but I think I've narrowed it down to crew_controller_slurm(), so only post that here:Reproducible example
Apologies @wlandau my initial example was not in fact reproducible, but while I see if I can make a minimal example, does this {targets} error give any clues as to what's going on? It occurs with or without
seconds_timeout
set increw.cluster::crew_controller_slurm()
Diagnostic information
The text was updated successfully, but these errors were encountered: