-
Notifications
You must be signed in to change notification settings - Fork 2
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
Extended wait command #130
Comments
That should be easy enough to implement, but what do you mean with "waits for any job"? Do you mean it should wait until all the users jobs are finished? Does that makes sense, what would be the usecase? I think it could be a bit dangerous, since "wait" is typed in quickly. Since there's no way within gricli (yet?) to cancel a running task -- (ctrl-c) exits gricli alltogether -- if a user did that accidently it could be quite inconvenient. I can see that there might be one for having a wait command where you can provide multiple jobs, though... |
+1 for a wait command (with job ID given) Not sure how useful would be waiting for "all jobs" (as bash wait would do) Might also be useful to have an all-in-one "submit"+"wait done"+"download-clean" |
there will probably be something like ${last_job_id} so: |
Can the wait be done on any job? Say, I submit a batch of 100s of jobs, and once I hit the point where I reach max cores, I wait for any job to finish - then submit another one... |
this is not smartest idea. let the scheduler deal with queues, so submit all your jobs without regard to max number of cores. |
Fair enough - ok, another use case (magma) - I start the job and don't care what the id is - I need the job to change state to active? |
that is what last_id will be for. Excerpts from reply+i-1392703-d4724197408b2c93d5f04ff1e57e7a935d8b6f56's message of Tue Aug 16 13:56:35 +1200 2011:
|
Sorry, I thought you referred to a particular job id, rather than a specific mentioning of last - without digging for the id. Point taken. |
How hard is it to implement wait job command, which does this:
The text was updated successfully, but these errors were encountered: