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
Unopinionated tools for running, debugging, testing and benchmarking Mojo apps.
git clone https://github.com/domokit/devtools.git
Devtools offers the following tools:
mojo_run - documentation - shell runnermojo_debug - documentation - debuggermojo_test - apptest runnermojo_benchmark - documentation - perf test runnerAdditionally, 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.
The library is canonically developed in the mojo repository, https://github.com/domokit/devtools is a mirror allowing to consume it separately.