72f6668eb7
In general, vars should only contain variables which are the same for all tasks. Variables specific to compilation belong in the build module (or compile recipe), and those specific to running tests belong in the flavor module, or the individual recipe which uses them. Bug: skia:6473 Change-Id: Ifd55a57118c5801e6f4934a6b5de9d1567415b9a Reviewed-on: https://skia-review.googlesource.com/128545 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com> |
||
|---|---|---|
| .. | ||
| android_compile.expected | ||
| bookmaker.expected | ||
| calmbench.expected | ||
| check_generated_files.expected | ||
| compile.expected | ||
| ct_skps.expected | ||
| housekeeper.expected | ||
| infra.expected | ||
| perf.expected | ||
| recreate_skps.expected | ||
| skpbench.expected | ||
| skqp_test.expected | ||
| test.expected | ||
| upload_calmbench_results.expected | ||
| upload_coverage_results.expected | ||
| upload_dm_results.expected | ||
| upload_nano_results.expected | ||
| upload_skiaserve.expected | ||
| android_compile.py | ||
| bookmaker.py | ||
| calmbench.py | ||
| check_generated_files.py | ||
| compile.py | ||
| ct_skps.py | ||
| housekeeper.py | ||
| infra.py | ||
| perf.py | ||
| README.md | ||
| recreate_skps.py | ||
| skpbench.py | ||
| skqp_test.py | ||
| test.py | ||
| upload_calmbench_results.py | ||
| upload_coverage_results.py | ||
| upload_dm_results.py | ||
| upload_nano_results.py | ||
| upload_skiaserve.py | ||
Skia Recipes
These are the top-level scripts which run inside of Swarming tasks to perform all of Skia's automated testing.
To run a recipe locally:
$ python infra/bots/recipes.py run --workdir=/tmp/<workdir> <recipe name without .py> key1=value1 key2=value2 ...
Each recipe may have its own required properties which must be entered as key/value pairs in the command.
When you change a recipe, you generally need to re-train the simulation test:
$ python infra/bots/recipes.py test run --train
Or:
$ cd infra/bots; make train
The test generates expectations files for the tests contained within each recipe which illustrate which steps would run, given a particular set of inputs. Pay attention to the diffs in these files when making changes to ensure that your change has the intended effect.