diff options
| author | Allan Sandfeld Jensen <allan.jensen@qt.io> | 2020-10-12 14:27:29 +0200 |
|---|---|---|
| committer | Allan Sandfeld Jensen <allan.jensen@qt.io> | 2020-10-13 09:35:20 +0000 |
| commit | c30a6232df03e1efbd9f3b226777b07e087a1122 (patch) | |
| tree | e992f45784689f373bcc38d1b79a239ebe17ee23 /chromium/docs/gpu/gpu_testing.md | |
| parent | 7b5b123ac58f58ffde0f4f6e488bcd09aa4decd3 (diff) | |
| download | qtwebengine-chromium-85-based.tar.gz | |
BASELINE: Update Chromium to 85.0.4183.14085-based
Change-Id: Iaa42f4680837c57725b1344f108c0196741f6057
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
Diffstat (limited to 'chromium/docs/gpu/gpu_testing.md')
| -rw-r--r-- | chromium/docs/gpu/gpu_testing.md | 17 |
1 files changed, 10 insertions, 7 deletions
diff --git a/chromium/docs/gpu/gpu_testing.md b/chromium/docs/gpu/gpu_testing.md index a2d9b20470d..958801a0f14 100644 --- a/chromium/docs/gpu/gpu_testing.md +++ b/chromium/docs/gpu/gpu_testing.md @@ -278,11 +278,11 @@ being tested. This *should* mean that the pixel tests will automatically work when run locally. However, if the local run detection code fails for some reason, you can manually pass some flags to force the same behavior: -In order to get around the local run issues, simply pass the `--local-run=1` -flag to the tests. This will disable uploading, but otherwise go through the -same steps as a test normally would. Each test will also print out `file://` -URLs to the produced image, the closest image for the test known to Gold, and -the diff between the two. +In order to get around the local run issues, simply pass the +`--local-pixel-tests` flag to the tests. This will disable uploading, but +otherwise go through the same steps as a test normally would. Each test will +also print out `file://` URLs to the produced image, the closest image for the +test known to Gold, and the diff between the two. Because the image produced by the test locally is likely slightly different from any of the approved images in Gold, local test runs are likely to fail during @@ -292,7 +292,7 @@ comparison. When using `--no-skia-gold-failure`, you'll also need to pass the `--passthrough` flag in order to actually see the link output. Example usage: -`run_gpu_integration_test.py pixel --no-skia-gold-failure --local-run=1 +`run_gpu_integration_test.py pixel --no-skia-gold-failure --local-pixel-tests --passthrough` If, for some reason, the local run code is unable to determine what the git @@ -300,7 +300,7 @@ revision is, simply pass `--git-revision aabbccdd`. Note that `aabbccdd` must be replaced with an actual Chromium src revision (typically whatever revision origin/master is currently synced to) in order for the tests to work. This can be done automatically using: -``run_gpu_integration_test.py pixel --no-skia-gold-failure --local-run +``run_gpu_integration_test.py pixel --no-skia-gold-failure --local-pixel-tests --passthrough --git-revision `git rev-parse origin/master` `` ## Running Binaries from the Bots Locally @@ -628,6 +628,9 @@ Here are some examples: * A change to Blink's memory purging primitive which caused intermittent timeouts of WebGL conformance tests on all platforms ([Issue 840988](http://crbug.com/840988)). +* Screen DPI being inconsistent across seemingly identical Linux machines, + causing the Maps pixel test to flakily produce incorrectly sized images + ([Issue 1091410](https://crbug.com/1091410)). If you notice flaky test failures either on the GPU waterfalls or try servers, please file bugs right away with the component Internals>GPU>Testing and |