-
Notifications
You must be signed in to change notification settings - Fork 25
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
Wait for specified job to get in running status #74
Comments
@wlad i think there might be an interesting solution for you based on something i am currently building. give me this weekend to confirm that it will work :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi @roopakv! As discussed here you wanted to check if this is possible. To be clear: it is possible to wait for a job to get in "running" status, but it does not solve my particular problem.
So what is my problem
I have 12 concurrent test jobs. Due to the nature of the free trier plan for open source project only 4 of them start simultaneously (the others are queued). I want to make sure that the one job that takes the most time starts first among the 12 concurrent jobs. The idea behind that is to ensure the shortest execution path.
what I have tried so far
Here is what I've tried so far with your wait_for_job command --> ehrbase/ehrbase@3f75552#diff-1d37e48f9ceff6d8030570cd36286a61R1586-R1675
The text was updated successfully, but these errors were encountered: