Currently, when Cullen Doyle (@cullendoyle28) tests romulan in workflows:
- specifying
--timeout by itself doesn't do anything or, if it does the program still defaults to 500 max cycles
- we should decide whether or not:
--max-cycles and --timeout are exclusive (I think so; we shouldn't provide both)
--timeout independent of --max-cycles should just timeout
- providing no flags runs an infinite loop (unless we see a stop)
Currently, when Cullen Doyle (@cullendoyle28) tests
romulanin workflows:--timeoutby itself doesn't do anything or, if it does the program still defaults to500max cycles--max-cyclesand--timeoutare exclusive (I think so; we shouldn't provide both)--timeoutindependent of--max-cyclesshould just timeout