1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
|
Tree Sheriffs Documentation
===========================
### Contents ###
* [What does a sheriff do?](#what_is_a_sheriff)
+ [Skia tree](#skia_tree)
+ [DEPS rolls](#deps_rolls)
+ [Gold and Perf](#gold_and_perf)
+ [Documentation](#sheriff_doc)
* [View current and upcoming sheriffs](#view_current_upcoming_sheriffs)
* [How to swap sheriff shifts](#how_to_swap)
* [Tips for sheriffs](#tips)
+ [When to file bugs](#when_to_file_bugs)
+ [How to close or re-open the tree](#how_close_tree)
+ [Compile bot failures automatically close the tree](#tree_closers)
+ [How to revert a CL](#how_to_revert)
+ [What to do if DEPS roll fails to land](#deps_roll_failures)
+ [How to rebaseline](#how_to_rebaseline)
<a name="what_is_a_sheriff"></a>
What does a sheriff do?
-----------------------
A sheriff keeps an eye on the tree, DEPS rolls, Gold tool and the Perf tool.
Below is a brief summary of what the sheriff does for each task:
<a name="skia_tree"></a>
### Skia tree
* Understand the [testing infrastructure](https://skia.org/dev/testing/automated_testing).
* Start watching the [status page](https://status.skia.org) for bot breakages.
* Track down people responsible for breakages and revert broken changes if there is no easy fix. You can use [blamer](#blamer) to help track down such changes.
* Close and open the [tree](http://skia-tree-status.appspot.com).
* Keep the builder comments on the [status page](https://status.skia.org) up to date.
* File or follow up with [BreakingTheBuildbots bugs](https://bug.skia.org/?q=label:BreakingTheBuildbots). See the tip on [when to file bugs](#when_to_file_bugs).
<a name="blamer"></a>
### Blamer
If you have Go installed, a command-line tool is available to search through
git history and do text searches on the full patch text and the commit
message. To install blamer run:
go get go.skia.org/infra/blamer/go/blamer
Then run blamer from within a Skia checkout. For example, to search if the
string "SkDevice" has appeared in the last 10 commits:
$ $GOPATH/bin/blamer --match SkDevice --num 10
commit ea70c4bb22394c8dcc29a369d3422a2b8f3b3e80
Author: robertphillips <robertphillips@google.com>
Date: Wed Jul 20 08:54:31 2016 -0700
Remove SkDevice::accessRenderTarget virtual
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2167723002
Review-Url: https://codereview.chromium.org/2167723002
<a name="deps_rolls"></a>
### DEPS rolls
* Ensure that [AutoRoll Bot](https://autoroll.skia.org)'s DEPS rolls land successfully.
<a name="gold_and_perf"></a>
### Gold and Perf
* Pay attention for new [Perf](https://perf.skia.org/) and [Gold](https://gold.skia.org/) alerts (by clicking on the bell at the top right of the [status page](https://status.skia.org)).
* The sheriff's duty here is to make sure that when developers introduce new images or new perf regressions, that they are aware of what happened, and they use these tools to take appropriate action.
<a name="sheriff_doc"></a>
### Documentation
* Improve/update this documentation page for future sheriffs, especially the [Tips section](#tips).
In general, sheriffs should have a strong bias towards actions that keep the tree green and then open; if a simple revert can fix the problem, the sheriff <b>should revert first and ask questions later</b>.
<a name="view_current_upcoming_sheriffs"></a>
View current and upcoming sheriffs
----------------------------------
The list of sheriffs is specified in the [skia-tree-status web app](https://skia-tree-status.appspot.com/sheriff). The current sheriff is highlighted in green.
The banner on the top of the [status page](https://status.skia.org) also displays the current sheriff.
<a name="how_to_swap"></a>
How to swap sheriff shifts
--------------------------
If you need to swap shifts with someone (because you are out sick or on vacation), please get approval from the person you want to swap with. Then send an email to skiabot@google.com to have someone make the database change (or directly ping rmistry@).
<a name="tips"></a>
Tips for sheriffs
-----------------
<a name="when_to_file_bugs"></a>
### When to file bugs
Pay close attention to the "Failures" view in the [status page](https://status.skia.org).
Look at all existing [BreakingTheBuildbots bugs](https://bug.skia.org/?q=label:BreakingTheBuildbots). If the list is kept up to date then it should accurately represent everything that is causing failures. If it does not, then please file/update bugs accordingly.
<a name="how_close_tree"></a>
### How to close or re-open the tree
1. Go to [skia-tree-status.appspot.com](https://skia-tree-status.appspot.com).
2. Change the status.
* To close the tree, include the word "closed" in the status.
* To open the tree, include the word "open" in the status.
* To caution the tree, include the word "caution" in the status.
<a name="how_to_submit_when_tree_closed"></a>
### How to submit when the tree is closed
* Submit manually using the "git cl land" with the --bypass-hooks flag.
* Add "No-Tree-Checks: true" to your CL description and use the CQ as usual.
<a name="tree_closers"></a>
### Compile bot failures automatically close the tree
A failure of the build steps in all compile bots automatically closes the tree. Sheriffs will have to manually reopen the tree when they deem the problem fixed.
Note: The tree is not closed automatically if the last run of the failed compile builder had the same failing step. The tree is also not closed if the tree was automatically closed less than 10 mins ago. If the tree is already closed then no action is taken.
<a name="how_to_revert"></a>
### How to revert a CL
See the revert documentation [here](https://skia.org/dev/contrib/revert).
<a name="deps_roll_failures"></a>
### What to do if DEPS roll fails to land
A common cause of DEPS roll failures are layout tests. Find the offending Skia CL by examining the commit hash range in the DEPS roll and revert (or talk to the commit author if they are available). If you do revert then keep an eye on the next DEPS roll to make sure it succeeds.
If a Skia CL changes layout tests, but the new images look good, the tests need to be rebaselined. See [Rebaseline Layout Tests](#how_to_rebaseline).
<a name="how_to_rebaseline"></a>
### Rebaseline Layout Tests (i.e., add suppressions)
* First create a Chromium bug:
* goto [crbug.com](https://crbug.com)
* Make sure you’re logged in with your Chromium credentials
* Click “New Issue”
* Summary: “Skia image rebaseline”
* Description:
* DEPS roll #,
* Helpful message about what went wrong (e.g., “Changes to how lighting is scaled in Skia r#### changed the following images:”)
* Layout tests affected
* You should copy the list of affected from stdio of the failing bot
* Status: Assigned
* Owner: yourself
* cc: reed@, bsalomon@, robertphillips@ & developer responsible for changes
* Labels: OS-All & Cr-Blink-LayoutTests
* If it is filter related, cc senorblanco@
* (Dispreferred but faster) Edit [skia/skia_test_expectations.txt](https://chromium.googlesource.com/chromium/src/+/master/skia/skia_test_expectations.txt)
* Add # comment about what has changed (I usually paraphrase the crbug text)
* Add line(s) like the following after the comment:
* crbug.com/<bug#youjustcreated> foo/bar/test-name.html [ ImageOnlyFailure ]
* Note: this change is usually done in the DEPS roll patch itself
* (Preferred but slower) Make a separate Blink patch by editing LayoutTests/TestExpectations
* Add # comment about what has changed (I usually paraphrase the crbug text)
* Add line(s) like the following after the comment:
* crbug.com/<bug#youjustcreated> foo/bar/test-name.html [ NeedsManualRebaseline ]
* Commit the patch you created and wait until it lands and rolls into Chrome
* Retry the DEPS roll (for the 1st/dispreferred option this usually means just retrying the layout bots)
* Make a Blink patch by editing LayoutTests/TestExpectations
* Add # comment about what has changed
* Add line(s) like the following after the comment:
* crbug.com/<bug#youjustcreated> foo/bar/test-name.html [ NeedsRebaseline ]
* (if you took the second option above you can just edit the existing line(s))
* If you took the first/dispreferred option above:
* Wait for the Blink patch to roll into Chrome
* Create a Chrome patch that removes your suppressions from skia/skia_test_expectations.txt
|
