OLD | NEW |
---|---|
(Empty) | |
1 # Failures of any GM tests listed in this file will be ignored, as if they | |
epoger
2013/09/19 15:02:52
The buildbots don't know to look for this file yet
epoger
2013/09/19 16:13:44
... and that separate CL is https://codereview.chr
| |
2 # had been marked "ignore-failure": true in the per-builder | |
3 # expected-results.json files. | |
4 # | |
5 # The idea is that, if you modify a GM test in such a way that you know it will | |
6 # require rebaselines on multiple platforms, you should add that test's name to | |
7 # this list within the same CL that modifies the test. | |
8 # Then, AS SOON AS POSSIBLE, you should rebaseline the tests (they will show up | |
9 # as status "failure-ignored") and remove the line you added to this file. | |
10 # If there are any lingering failures that need to be suppressed (ignored), you | |
11 # MUST move those suppressions into the per-builder expected-results.json files. | |
12 # | |
13 # Any lines starting with '#' are comments and will be ignored. | |
14 # Other than that, each line must either be whitespace or list just one test. | |
15 # | |
16 # For more information, see https://code.google.com/p/skia/issues/detail?id=1600 | |
17 # ('GM expectations: create tool to suppress failures until new baselines are | |
18 # checked in') | |
19 | |
20 # EXAMPLE: (remove the first '#' on each line) | |
21 ## Added by edisonn as part of https://codereview.chromium.org/23851037/ | |
22 #gradients | |
OLD | NEW |