diff options
| -rw-r--r-- | site/docs/skylark/bzl-style.md | 2 | ||||
| -rw-r--r-- | site/docs/skylark/performance.md | 2 |
2 files changed, 0 insertions, 4 deletions
diff --git a/site/docs/skylark/bzl-style.md b/site/docs/skylark/bzl-style.md index a76d8aa864..9a7d7048db 100644 --- a/site/docs/skylark/bzl-style.md +++ b/site/docs/skylark/bzl-style.md @@ -40,8 +40,6 @@ is to make your files easy to process, both by humans and tools. ## General advice * Use [skylint](skylint.md) ---> - ## Style diff --git a/site/docs/skylark/performance.md b/site/docs/skylark/performance.md index ac36888db8..9b77a01433 100644 --- a/site/docs/skylark/performance.md +++ b/site/docs/skylark/performance.md @@ -207,7 +207,6 @@ You must pass these two startup flags to *every* Bazel invocation: ``` **NOTE**: The bazel repository comes with an allocation instrumenter. Make sure to adjust '$(BAZEL)' for your repository location. ---> These start the server in memory tracking mode. If you forget these for even one Bazel invocation the server will restart and you will have to start over. @@ -260,7 +259,6 @@ Next, we use the `pprof` tool to investigate the heap. A good starting point is getting a flame graph by using `pprof -flame $HOME/prof.gz`. You can get `pprof` from https://github.com/google/pprof. ---> In this case we get a text dump of the hottest call sites annotated with lines: |