| commit | 5ca37713d6133202f8c6ff23c983f90f4b1e5dd8 | [log] [tgz] |
|---|---|---|
| author | Przemyslaw Pietrzkiewicz <ppi@chromium.org> | Thu Jun 11 18:33:31 2015 +0200 |
| committer | Przemyslaw Pietrzkiewicz <ppi@chromium.org> | Thu Jun 11 18:33:31 2015 +0200 |
| tree | 5468a4fd3b97fe47e66729f3fe8b150caf7ae4f4 | |
| parent | 74731b06d3f9f5a915186cf36ab0475c0947ad0b [diff] |
Teach `debugger tracing stop` to pick a file name automatically. This will make the tracing write its result to the first available filename of [mojo_trace_000.json, mojo_trace_001.json, ...]. (we always had a 'default' set on the |file_name| parameter, but it didn't actually work as the parameter was positional and hence required by default) Fixes domokit/devtools#13. R=tonyg@chromium.org Review URL: https://codereview.chromium.org/1184453002. Cr-Mirrored-From: https://github.com/domokit/mojo Cr-Mirrored-Commit: 64a4a80012dbfd6ffdc1c50a922cebca36dae341
Unopinionated tools for running, debugging and testing Mojo apps.
The repo consists of:
As devtools carry no assumptions about build system or file layout being used, the primary way of using devtools now is to embed the functionality provided by devtoolslib in a thin wrapper script. For examples, one can refer to mojo's shell runner and apptest runner.
The set of executable scripts is WIP. We currently offer:
git clone https://github.com/domokit/devtools.git
The library is canonically developed in the mojo repository, https://github.com/domokit/devtools is a mirror allowing to consume it separately.