Building a feature to constrain the length of test campaign

[tianyin]

See the discussions at, https://piazza.com/class/lrgyb01xp5q10t/post/109 https://piazza.com/class/lrgyb01xp5q10t/post/110 https://piazza.com/class/lrgyb01xp5q10t/post/116 One more motive: https://piazza.com/class/lrgyb01xp5q10t/post/122

It's critical for first-time users.

The modes we should support:

1. Run a specified amount of time
2. Stop when the first alarm is reported
3. Stop when the first 10 alarms are reported
4. Output progress log messages by dynamically calculating the time and predict the remaining test run time

[tianyin]

I hope someone can do it as a 523 course project.

[rhl-bthr]

It might also be useful to display a ballpark ETA. My run for FoundationDB has been going on for the last ~16 hours, and I'm not sure how long it might still take.

[tianyin]

@rhl-bthr would you take this as your course project? :)

[tianyin]

One more motive: https://piazza.com/class/lrgyb01xp5q10t/post/122

[rguptavh]

I'd love to take this on if someone hasn't claimed it already