You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
@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 :)
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: