diff options
author | tomlu <tomlu@google.com> | 2017-10-12 03:18:29 +0200 |
---|---|---|
committer | Marcel Hlopko <hlopko@google.com> | 2017-10-12 10:16:47 +0200 |
commit | 39a7421816c8e92fa44d1368dae518d8cda7ac97 (patch) | |
tree | af524cb901030da43387d7ffe286df8d103ec756 | |
parent | f6b8d5e269cf64bda483af464ad98af7277728a6 (diff) |
Make blaze dump docs external.
The dump command is readily available from bazel, so I don't see why the docs should be closed.
PiperOrigin-RevId: 171904287
-rw-r--r-- | site/docs/user-manual.html | 47 |
1 files changed, 2 insertions, 45 deletions
diff --git a/site/docs/user-manual.html b/site/docs/user-manual.html index abf6253807..1773f45ba5 100644 --- a/site/docs/user-manual.html +++ b/site/docs/user-manual.html @@ -25,6 +25,8 @@ title: User Manual <a href='#canonicalize'>canonicalize-flags</a> Canonicalize Bazel flags. <a href='#clean'>clean</a> Removes output files and optionally stops the server. + <a href='#dump'>dump</a> Dumps the internal state of the Bazel server process. + <a href='#help'>help</a> Prints help for commands, or the index. <a href='#info'>info</a> Displays runtime info about the bazel server. @@ -3198,51 +3200,6 @@ adb -s deadbeef install ... printed to the console. </p> -<h3 id='analyze-profile'>The <code>analyze-profile</code> command</h3> - -<p> - The <code>analyze-profile</code> command analyzes data previously gathered - during the build using <code class='flag'>--profile</code> option. It provides several - options to either perform analysis of the build execution or export data in - the specified format. - -</p> -<p> - The following options are supported: -</p> -<ul> - <li><code id='flag--dump'>--dump=text</code> displays all gathered data in a - <a href='#dump-text-format'>human-readable format</a></li> - <li><code>--dump=raw</code> displays all gathered data in a - <a href='#dump-raw-format'>script-friendly format</a></li> - <li><code id='flag--html'>--html</code> generates an <a href='#dump-html-format'>HTML file</a> visualizing the - actions and rules executed in the build, as well as summary statistics for the build - <ul> - <li><code id='flag--html_details'>--html_details</code> adds more fine-grained - information on actions and rules to the HTML visualization</li> - <ul> - <li><code id='flag--html_histograms'>--html_histograms</code> adds histograms for Skylark - functions clicked in the statistics table. This will increase file size massively</li> - <li><code id='flag--nochart'>--nochart</code> hides the task chart from generated HTML - </li> - </ul> - </ul> - </li> - <li><code id='flag--combine'>--combine</code> combines multiple profile data files into a single - report. Does not generate HTML task charts</li> - <li><code id='flag--task_tree'>--task_tree</code> prints the tree of tasks matching the given - regular expression - <ul> - <li><code id='flag--task_tree_threshold'>--task_tree_threshold</code> skip tasks with duration - less than threshhold, in milliseconds. Default is 50ms</li> - </ul> - </li> -</ul> - -<p> - See the section on <a href='#profiling'>Troubleshooting performance by profiling</a> for - format details and usage help. - </p> <h3 id='canonicalize'>The <code>canonicalize-flags</code> command</h3> |