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
{{ message }}
This repository has been archived by the owner on Dec 3, 2018. It is now read-only.
It's my intention that we get a bunch of configs that we run before every release. Something that would make this easier would be having a PASS/FAIL condition, as well as a timeout. When running an antfarm config, if there is a timeout variable, the antfarm will shut-down all of the ants and issue a PASS/FAIL. The PASS condition is only issued if no ant has reported any errors, and the antfarm has also not reported any errors.
If no timeout is specified in the config, then the antfarm will just run until you tell it to quit. It will still state PASS/FAIL when you tell it to quit.
It's my intention that we get a bunch of configs that we run before every release. Something that would make this easier would be having a PASS/FAIL condition, as well as a timeout. When running an antfarm config, if there is a timeout variable, the antfarm will shut-down all of the ants and issue a PASS/FAIL. The PASS condition is only issued if no ant has reported any errors, and the antfarm has also not reported any errors.
If no timeout is specified in the config, then the antfarm will just run until you tell it to quit. It will still state PASS/FAIL when you tell it to quit.
The timeout is in minutes.
Example Config:
The text was updated successfully, but these errors were encountered: