| commit | 6f537ebb5e0552f224464f6827ea41667fce9976 | [log] [tgz] |
|---|---|---|
| author | Kai Ninomiya <[email protected]> | Wed Jan 04 23:43:47 2023 |
| committer | Chromium LUCI CQ <[email protected]> | Wed Jan 04 23:43:47 2023 |
| tree | fbc704250ab9d3c07ad17c625bdc22ced93cf564 | |
| parent | 51ec881fc379e1e21cbbc7c0daaf8e9b32bc96ff [diff] [blame] |
Update docs about code coverage on full Chromium Running full Chromium with code coverage no longer requires disabling the sandbox. It was fixed in 2019. Found while working on crbug.com/1399354 Bug: None, 972232 No-Try: True Change-Id: Ieeb86f162ebc0f955ace8d511ee3bf7c9b61cf92 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4129804 Reviewed-by: Zhaoyang Li <[email protected]> Commit-Queue: Kai Ninomiya <[email protected]> Cr-Commit-Position: refs/heads/main@{#1089024}
diff --git a/docs/testing/code_coverage.md b/docs/testing/code_coverage.md index ad2f0bb..9ddebd6f 100644 --- a/docs/testing/code_coverage.md +++ b/docs/testing/code_coverage.md
@@ -284,10 +284,9 @@ code coverage instrumentation enabled. However, there are some inconveniences involved: -* Linking may take a while -* The binary is huge (~4GB) -* The browser "works", but is noticeably slow and laggy -* The sandbox needs to be disabled (`--no-sandbox`) +* Linking may take a while, especially if you use a non-component build. +* The binary is huge (2-4GB). +* The browser may be noticeably slow and laggy. For more information, please see [crbug.com/834781].