Add GPU parallel jobs documentation

Adds a paragraph to the documentation on running GPU tests locally
about the --jobs argument since setting it is important for certain
test/platform combinations.

Bug: 1406875
Change-Id: I889811c76c4bd82b3f3568ae6b29d2dbd4058288
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4179648
Reviewed-by: Yuly Novikov <ynovikov@chromium.org>
Auto-Submit: Brian Sheedy <bsheedy@chromium.org>
Commit-Queue: Yuly Novikov <ynovikov@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1094626}

This commit is contained in:

Brian Sheedy

2023-01-19 20:00:33 +00:00

committed by

Chromium LUCI CQ

parent 50492356ca

commit 09356cf622

1 changed files with 9 additions and 0 deletions

									
										9

docs/gpu/gpu_testing.md
									
				@ -210,6 +210,15 @@ complain about being unable to find the browser binary on Android if you build

				in a non-standard output directory. Thus, `out/Release` or `out/Debug` are

				suggested when testing on Android.

				If you are running on a platform that does not support multiple browser

				instances at a time (Android or ChromeOS), it is also recommended that you pass

				in `--jobs=1`. This only has an effect on test suites that have parallel test

				support, but failure to pass in the argument for those tests on these platforms

				will result in weird failures due to multiple test processes stepping on each

				other. On other platforms, you are still free to specify `--jobs` to get more

				or less parallelization instead of relying on the default of one test process

				per logical core.

				**Note:** The tests require some third-party Python packages. Obtaining these

				packages is handled automatically by `vpython3`, and the script's shebang should

				use vpython if running the script directly. If you're used to invoking `python3`

Add GPU parallel jobs documentation

9 docs/gpu/gpu_testing.md

9

docs/gpu/gpu_testing.md