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 <zhaoyangli@chromium.org>
Commit-Queue: Kai Ninomiya <kainino@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1089024}

This commit is contained in:

Kai Ninomiya

2023-01-04 23:43:47 +00:00

committed by

Chromium LUCI CQ

parent 51ec881fc3

commit 6f537ebb5e

1 changed files with 3 additions and 4 deletions

									
										7

docs/testing/code_coverage.md
									
				@@ -284,10 +284,9 @@ Yes, with some important caveats. It is possible to build `chrome` target with

				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].

Update docs about code coverage on full Chromium

7 docs/testing/code_coverage.md

7

docs/testing/code_coverage.md