Google Git
Sign in
skia / skia / 1e6b36eb574d859c51968ff0c5bc3c17773857a1 / . / infra / bots / recipes
tree: 20070ddc42a1ba5dc7ffe69ae1487be66bd0a8f1 [path history] [tgz]
  1. bundle_recipes.expected/
  2. calmbench.expected/
  3. check_generated_files.expected/
  4. compile.expected/
  5. ct_skps.expected/
  6. housekeeper.expected/
  7. infra.expected/
  8. perf.expected/
  9. recreate_skps.expected/
  10. skpbench.expected/
  11. test.expected/
  12. update_meta_config.expected/
  13. upload_coverage_results.expected/
  14. upload_dm_results.expected/
  15. upload_nano_results.expected/
  16. bundle_recipes.py
  17. calmbench.py
  18. check_generated_files.py
  19. compile.py
  20. ct_skps.py
  21. housekeeper.py
  22. infra.py
  23. perf.py
  24. README.md
  25. recreate_skps.py
  26. skpbench.py
  27. test.py
  28. update_meta_config.py
  29. upload_coverage_results.py
  30. upload_dm_results.py
  31. upload_nano_results.py
infra/bots/recipes/README.md

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.