Make mojo_benchmark understand the output it is producing.

This patch:
 - refactors the logic in mojo_benchmark so that obtaining the output
   produced by `benchmark.mojo` is separated from its analysis and
   presentation
 - makes `mojo_benchmark` parse the measurements results, as opposed to
   just streaming the output produced by `benchmark.mojo`.

This is a prerequisite for producing the chart data to be uploaded to
the performance dashboard, see domokit/mojo#474. As a bonus, we now
notice when measurement result is missing and return non-zero exit code.

R=viettrungluu@chromium.org

Review URL: https://codereview.chromium.org/1392173006 .

Cr-Mirrored-From: https://github.com/domokit/mojo
Cr-Mirrored-Commit: 0acce94790935a282c3461c3fca2787e61bd2233
1 file changed
tree: 201e33fb04193d144f7d5bd2e29f32d2240cd8db
  1. android_gdb/
  2. android_stack_parser/
  3. devtoolslib/
  4. docs/
  5. .gitignore
  6. mojo_benchmark
  7. mojo_debug
  8. mojo_run
  9. mojo_test
  10. README.md
  11. remote_adb_setup
README.md

Devtools

Unopinionated tools for running, debugging, testing and benchmarking Mojo apps.

Install

git clone https://github.com/domokit/devtools.git

Contents

Devtools offers the following tools:

Additionally, remote_adb_setup script helps to configure adb on a remote machine to communicate with a device attached to a local machine, forwarding the ports used by mojo_run.

Development

The library is canonically developed in the mojo repository, https://github.com/domokit/devtools is a mirror allowing to consume it separately.