For example, the current !test repro runs for 1-day, which might be too short to uncover a rare issue. It would be convenient if there was an option to specify the duration of the repro test as well (with the default/no-option being the current 1-day). Of course, such a feature would mean that both the base and the PR'ed branch need to be run (instead of using the committed checksums from the base branch), and there might need to be some reasonable lower/upper limits set for the runs for repro tests.
May be other commands might also benefit from a generic solution to parse user-supplied-options.
@CodeGat
For example, the current
!test reproruns for 1-day, which might be too short to uncover a rare issue. It would be convenient if there was an option to specify the duration of the repro test as well (with the default/no-option being the current 1-day). Of course, such a feature would mean that both the base and the PR'ed branch need to be run (instead of using the committed checksums from the base branch), and there might need to be some reasonable lower/upper limits set for the runs for repro tests.May be other commands might also benefit from a generic solution to parse user-supplied-options.
@CodeGat