8d744124a6
Also simplify (i.e. remove) the "copy to tmp dir" step. Bug: skia: Change-Id: I88a12aeaa1ad131588f66ac306909ec892e5ad18 Reviewed-on: https://skia-review.googlesource.com/148021 Reviewed-by: Stephan Altmueller <stephana@google.com> Reviewed-by: Eric Boren <borenet@google.com> Commit-Queue: Kevin Lubick <kjlubick@google.com> |
||
|---|---|---|
| .. | ||
| android_compile.expected | ||
| bookmaker.expected | ||
| calmbench.expected | ||
| check_generated_files.expected | ||
| compile.expected | ||
| compute_test.expected | ||
| ct_skps.expected | ||
| housekeeper.expected | ||
| infra.expected | ||
| perf.expected | ||
| recreate_skps.expected | ||
| skpbench.expected | ||
| skqp_test.expected | ||
| test_pathkit.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 | ||
| compute_test.py | ||
| ct_skps.py | ||
| housekeeper.py | ||
| infra.py | ||
| perf.py | ||
| README.md | ||
| recreate_skps.py | ||
| skpbench.py | ||
| skqp_test.py | ||
| test_pathkit.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 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.