aboutsummaryrefslogtreecommitdiffhomepage
path: root/site/dev
diff options
context:
space:
mode:
authorGravatar hcm <hcm@google.com>2016-09-22 12:47:14 -0700
committerGravatar Commit bot <commit-bot@chromium.org>2016-09-22 12:47:14 -0700
commit3d89a7c0d28c4b9312b10149037f2fdac5dc5985 (patch)
tree0e8e7fe6e571599a656f0f556629f62f8179f16c /site/dev
parent8c170971f182d47bc9af71fc88a607740d03dfd5 (diff)
Update Chrome section to include Skia roll/sheriff/bug info
Diffstat (limited to 'site/dev')
-rw-r--r--site/dev/chrome/index.md18
-rw-r--r--site/dev/testing/skps.md65
-rw-r--r--site/dev/testing/testing.md2
3 files changed, 18 insertions, 67 deletions
diff --git a/site/dev/chrome/index.md b/site/dev/chrome/index.md
index ba9dcdfa6f..d715304f32 100644
--- a/site/dev/chrome/index.md
+++ b/site/dev/chrome/index.md
@@ -1,5 +1,21 @@
Skia in Chrome
==============
+Changes to the Skia repository will be rolled into Chromium (and Blink) by the
+AutoRoll bot several times per day.
+
If you have a Skia change that needs to be tested in Chrome or Blink, or which
-requires associated changes in those repositories, this is the place for you.
+requires associated changes in those repositories, see the guides in this
+section for tips on execution.
+
+For problems in Chromium related to Skia rolls:
+
+ * Go to https://autoroll.skia.org. Login with google.com account and click
+ the STOP button to pause new rolls.
+ * Revert the offending DEPS roll.
+ * If an obvious owner cannot be found in the list of CLs, assign to the Skia
+ Sheriff, listed at the top of https://status.skia.org and as a reviewer
+ on the roll CL.
+ * If the Sheriff cannot be assigned, cc them and assign the issue to hcm@.
+
+For more tips on bug triage and labeling, see the [Issue Tracker page](../../user/issue-tracker/).
diff --git a/site/dev/testing/skps.md b/site/dev/testing/skps.md
deleted file mode 100644
index 2d890de193..0000000000
--- a/site/dev/testing/skps.md
+++ /dev/null
@@ -1,65 +0,0 @@
-Downloading SKPs
-================
-
-### Contents ###
-
-* [Overview](#overview)
-* [How to download SKPs](#download_skps)
- + [Buildbot SKPs (for Googlers)](#buildbot_skps_googler)
- + [Buildbot SKPs (for trusted partners)](#buildbot_skps_partners)
- + [Cluster Telemetry SKPs (for Googlers)](#ct_skps_googler)
-
-<a name="overview"></a>
-Overview
---------
-
-An SKP is a binary representation of the draw commands Chromium sends to Skia for rasterization.
-
-Skia uses different types of SKPs in our continuous builds and tests:
-
-* [Buildbot](https://skia.org/dev/testing/buildbot) SKPs are the small set (89 as of 2/10/16) of SKPs that are used on almost all our bots.
-* [Cluster Telemetry](https://skia.org/dev/testing/ct) SKPs are the much larger set (~900k) that are used by our CT bots (Eg: [CT_BENCH_10k](https://build.chromium.org/p/client.skia/builders/Perf-Ubuntu-GCC-GCE-CPU-AVX2-x86_64-Release-CT_BENCH_10k_SKPs), [CT_DM_10k](https://build.chromium.org/p/client.skia/builders/Test-Ubuntu-GCC-GCE-CPU-AVX2-x86_64-Debug-CT_DM_10k_SKPs), [CT_DM_1m](https://build.chromium.org/p/client.skia.fyi/builders/Test-Ubuntu-GCC-GCE-CPU-AVX2-x86_64-Debug-CT_DM_1m_SKPs)).
-
-Skia developers find it useful to download these SKPs to run local tests to reproduce problems seen on the buildbots. The below sections detail how to download them.
-
-<a name="download_skps"></a>
-How to download SKPs
---------------------
-
-<a name="buildbot_skps_googler"></a>
-### Buildbot SKPs (for Googlers)
-
-The following will work only if you have a google.com account.
-
-All buildbot SKP files created by the RecreateSKPs bot are available via the asset management scripts:
-
- $ download_from_google_storage -s infra/bots/tools/luci-go/${PLATFORM}/cipd.sha1 --bucket chromium-luci
- $ infra/bots/tools/luci-go/${PLATFORM}/cipd auth-login
- $ infra/bots/assets/skp/download.py -t ${TARGET_DIR}
-
-Note: If you are on Windows, you will need to specify *cipd.exe.sha1*, not *cipd.sha1*
-
-<a name="buildbot_skps_partners"></a>
-### Buildbot SKPs (for trusted partners)
-
-* Request access to the gs://chrome-partner-telemetry bucket by emailing telemetry@chromium.org ([example](https://groups.google.com/a/chromium.org/d/msg/telemetry/kSwcgH7KiYs/zwBwEZaadOIJ)).
-* Once approved you can download Skia's weekly refreshed buildbot SKPs from gs://chrome-partner-telemetry/skps
-
-
-<a name="ct_skps_googler"></a>
-### Cluster Telemetry SKPs (for Googlers)
-
-The following will work only if you have a google.com account.
-
-* Download the gsutil tool https://developers.google.com/cloud/sdk/#Quick_Start.
-* Authenticate using your google.com credentials “gcloud auth login”
-* Look at the SKP Repository list [here](https://ct.skia.org/lua_script/) for all available SKPs.
-* Run in your terminal:
-
- $ SKP\_DEST=...<br/>
- $ REPO\_TYPE=... (Either All, 100k, Mobile10k, 10k, Dummy1k)<br/>
- $ CHROMIUM\_BUILD=... (Eg: fad657e-276e633)<br/>
- $ gsutil -m cp gs://cluster-telemetry/swarming/skps/${REPO\_TYPE}/${CHROMIUM\_BUILD}/{1..10}/*.skp ${SKP\_DEST}
-
-* Substitute the 1 and 10 above with the start and end ranks of the SKPs you want to copy locally.
-* If you are trying to find a particular SKP. Look for it in the CSV [here](https://pantheon.corp.google.com/m/cloudstorage/b/cluster-telemetry/o/csv/top-1m.csv) and then use that rank in the copy command.
diff --git a/site/dev/testing/testing.md b/site/dev/testing/testing.md
index 667e822d5e..e577a51231 100644
--- a/site/dev/testing/testing.md
+++ b/site/dev/testing/testing.md
@@ -51,7 +51,7 @@ configuration you might be expecting it to run.
Don't worry about the "skps: Couldn't read skps." messages either, you won't
have those by default and can do without them. If you wish to test with them
-too, you can [download them separately](https://skia.org/dev/testing/skps).
+too, you can download them separately.
The next line is an overview of the work DM is about to do.
~~~