-
Notifications
You must be signed in to change notification settings - Fork 154
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
required a support adding new flag which will wait before trigger next suite #592
Comments
- Fixed initial implementation - Updated documentation
Hi @kbogineni ! The Any feedback is highly appreciated! 😊 |
@joonaskuisma how the pabot command looks if this is fixed |
Here is section of updated README.md (You can find it my fork and feature branch also): By using the command #SLEEP X, where X is an integer in the range [0-3600] (in seconds), you can define a startup delay for each subprocess. #SLEEP affects the next line unless the next line starts a group with {, in which case the delay applies to the entire group. If the next line begins with --test or --suite, the delay is applied to that specific item. Any other occurrences of #SLEEP are ignored. The following example clarifies the behavior:
where order.txt is:
prints something like this:
|
Hi @kbogineni ! What you think about this solution? (See my previous comment) |
Hi
I am using pabot for robot parallel execution and I have a requirement of executing the suites in parallel but need to some time to between each suite. For example, I have suite1 and suite2 and I need to trigger them with some delay as below
Suite1 and wait $DELAY and Suite2
Could you please look at this and implement? it will be helpful for others also
The text was updated successfully, but these errors were encountered: