Update GPU documentation links
Updates the following in the GPU documentation: 1. Links to the Skia Gold instance. There were still references to the old chrome-gpu-gold.skia.org instance that has been gone for a long time. 2. Links to the pixel_wrangling.md documentation, which has been moved to various internal documentation pages. Bug: 1250846 Change-Id: Ib72b870c91a8048bbe4568256ff1845c2d72d7a0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3173927 Auto-Submit: Brian Sheedy <bsheedy@chromium.org> Commit-Queue: Yuly Novikov <ynovikov@chromium.org> Reviewed-by: Yuly Novikov <ynovikov@chromium.org> Cr-Commit-Position: refs/heads/main@{#924044}
This commit is contained in:

committed by
Chromium LUCI CQ

parent
555c3b53c3
commit
5a4c0a39d1
@ -8,7 +8,7 @@ sections ([1][pixel debugging], [2][pixel updating]) of the general GPU testing
|
||||
documentation.
|
||||
|
||||
[local pixel testing]: gpu_testing.md#Running-the-pixel-tests-locally
|
||||
[GPU Pixel Wrangling]: pixel_wrangling.md
|
||||
[GPU Pixel Wrangling]: http://go/gpu-pixel-wrangler
|
||||
[pixel debugging]: gpu_testing.md#Debugging-Pixel-Test-Failures-on-the-GPU-Bots
|
||||
[pixel updating]: gpu_testing.md#Updating-and-Adding-New-Pixel-Tests-to-the-GPU-Bots
|
||||
|
||||
@ -125,9 +125,9 @@ the CL was merged as. In the above example, if the CL was merged as commit
|
||||
You can see all currently untriaged images that are currently being produced on
|
||||
ToT on the [GPU Gold instance's main page][gpu gold instance] and currently
|
||||
untriaged images for a CL by substituting the Gerrit CL number into
|
||||
`https://chrome-gpu-gold.skia.org/search?issue=[CL Number]&unt=true&master=true`.
|
||||
`https://chrome-gold.skia.org/search?issue=[CL Number]&unt=true&master=true`.
|
||||
|
||||
[gpu gold instance]: https://chrome-gpu-gold.skia.org
|
||||
[gpu gold instance]: https://chrome-gold.skia.org
|
||||
|
||||
It's possible, particularly if a test is regularly producing multiple images,
|
||||
for an image to be untriaged but not show up on the front page of the Gold
|
||||
@ -135,7 +135,7 @@ instance (for details, see [this crbug comment][untriaged non tot comment]). To
|
||||
see all such images, visit [this link][untriaged non tot].
|
||||
|
||||
[untriaged non tot comment]: https://bugs.chromium.org/p/skia/issues/detail?id=9189#c4
|
||||
[untriaged non tot]: https://chrome-gpu-gold.skia.org/search?fdiffmax=-1&fref=false&frgbamax=255&frgbamin=0&head=false&include=false&limit=50&master=false&match=name&metric=combined&neg=false&offset=0&pos=false&query=source_type%3Dchrome-gpu&sort=desc&unt=true
|
||||
[untriaged non tot]: https://chrome-gold.skia.org/search?fdiffmax=-1&fref=false&frgbamax=255&frgbamin=0&head=false&include=false&limit=50&master=false&match=name&metric=combined&neg=false&offset=0&pos=false&query=source_type%3Dchrome-gpu&sort=desc&unt=true
|
||||
|
||||
### Finding A Failed Build
|
||||
|
||||
@ -160,7 +160,7 @@ shard number.
|
||||
|
||||
If for some reason an image is not showing up in Gold but you know the hash, you
|
||||
can manually navigate to the page for it by filling in the correct information
|
||||
to `https://chrome-gpu-gold.skia.org/detail?test=[test_name]&digest=[hash]`.
|
||||
to `https://chrome-gold.skia.org/detail?test=[test_name]&digest=[hash]`.
|
||||
From there, you should be able to triage it as normal.
|
||||
|
||||
If this happens, please also file a bug in [Skia's bug tracker][skia crbug] so
|
||||
|
@ -86,7 +86,7 @@ overview of this documentation and links back to various portions.
|
||||
Please see the [GPU Pixel Wrangling instructions] for links to dashboards
|
||||
showing the status of various bots in the GPU fleet.
|
||||
|
||||
[GPU Pixel Wrangling instructions]: pixel_wrangling.md#Fleet-Status
|
||||
[GPU Pixel Wrangling instructions]: http://go/gpu-pixel-wrangler#fleet-status
|
||||
|
||||
## Using the GPU Bots
|
||||
|
||||
@ -565,7 +565,7 @@ you will have to approve new images. Simply run your CL through the CQ and
|
||||
follow the steps outline [here][pixel wrangling triage] under the "Check if any
|
||||
pixel test failures are actual failures or need to be rebaselined." step.
|
||||
|
||||
[pixel wrangling triage]: pixel_wrangling.md#How-to-Keep-the-Bots-Green
|
||||
[pixel wrangling triage]: http://go/gpu-pixel-wrangler-info#how-to-keep-the-bots-green
|
||||
|
||||
If you are adding a new pixel test, it is beneficial to set the
|
||||
`grace_period_end` argument in the test's definition. This will allow the test
|
||||
@ -674,4 +674,4 @@ include links to the failing builds and copies of the logs, since the logs
|
||||
expire after a few days. [GPU pixel wranglers] should give the highest priority
|
||||
to eliminating flakiness on the tree.
|
||||
|
||||
[GPU pixel wranglers]: pixel_wrangling.md
|
||||
[GPU pixel wranglers]: http://go/gpu-pixel-wrangler
|
||||
|
@ -717,7 +717,7 @@ seems worthwhile to continuously test the "next" version of graphics drivers as
|
||||
well as the current stable ones.
|
||||
|
||||
[sample driver cl]: https://chromium-review.googlesource.com/c/chromium/src/+/1726875
|
||||
[updating gold baselines]: https://chromium.googlesource.com/chromium/src/+/HEAD/docs/gpu/pixel_wrangling.md#how-to-keep-the-bots-green
|
||||
[updating gold baselines]: http://go/gpu-pixel-wrangler-info#how-to-keep-the-bots-green
|
||||
|
||||
## Credentials for various servers
|
||||
|
||||
|
@ -91,9 +91,11 @@ Please create a saved query in Monorail for `component:Blink>WebGL` and select
|
||||
|
||||
This is intended to be a lightweight rotation that shouldn't take too much of
|
||||
the triager's time. For this reason it's scheduled independently of other shifts
|
||||
like [pixel wrangling](pixel_wrangling.md), and may overlap. If any conflicts do
|
||||
like [pixel wrangling], and may overlap. If any conflicts do
|
||||
arise, please reach out or swap shifts.
|
||||
|
||||
[pixel wrangling]: http://go/gpu-pixel-wrangler
|
||||
|
||||
The rotation is [managed
|
||||
here](https://rotations.corp.google.com/rotation/6257611988008960) via the
|
||||
Google-internal rotations tool. Shift swaps are managed via the tool. The
|
||||
|
Reference in New Issue
Block a user