diff options
| author |  twerth <twerth@google.com> | 2018-03-05 01:32:50 -0800 |
|---|---|---|
| committer |  Copybara-Service <copybara-piper@google.com> | 2018-03-05 01:34:56 -0800 |
| commit | 700bc13e4e63c643d2df715994a7d331e4deefba (patch) | |
| tree | 819564a218322d197e551df3b15e31bb2a9dd7b8 /site/docs/user-manual.html | |
| parent | c3916f9ac1384c5f3bc6e4b3f1342db3af0dbab8 (diff) | |
Add documentation for the action graph dump command.
RELNOTES: None
PiperOrigin-RevId: 187834884
Diffstat (limited to 'site/docs/user-manual.html')
| -rw-r--r-- | site/docs/user-manual.html | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/site/docs/user-manual.html b/site/docs/user-manual.html index e817628c9e..f59e18a9aa 100644 --- a/site/docs/user-manual.html +++ b/site/docs/user-manual.html @@ -3383,6 +3383,16 @@ adb -s deadbeef install ... <li><code class='flag'>--skylark_memory</code> dumps a <href a=https://github.com/google/pprof>pprof</href> compatible .gz file to the specified path. You must enable memory tracking for this to work.</li> + <li><code class='flag'>--action_graph=/path/to/file</code> dumps the state of + the internal Bazel action graph in proto format to + <code>/path/to/file</code>. You have to run (at least) the analysis phase + for the targets you are interested in (for example, <code>bazel build --nobuild + //foo:bar</code>). Note that this feature is still experimental, subject to + change and will probably be integrated into <code>cquery</code> in the + future. + <li><code class='flag'>--action_graph:targets=target1,target2,...</code> + filters the actions to the comma-separated list of targets when dumping the + action graph.</li> </ul> <h4 id='memory-tracking'>Memory tracking</h4> |