We need to spend time playing around with the new runner (that's what you get
when USE_CANARY_CALIPER is set to any nonempty value).
1. Try every user mistake we can think of and make sure the error is helpful
2. Try every valid variation we can think of and make sure the scenario
selection it reports is what we expected (can ctrl-C and not actually run the
benchmark if desired)
3. For valid benchmarks that run, what do you think of the output? Do you find
it totally clear or are you in any way confused by it? If the latter, there
may be something we should fix.
Original issue reported on code.google.com by kevinb@google.com on 8 May 2012 at 9:22
Original issue reported on code.google.com by
kevinb@google.com
on 8 May 2012 at 9:22