Google Git
Sign in
skia / skia / 644341af03d22dfe10e8e6c47e0aa21f5346031b / . / infra / bots / recipes
tree: 723138e6bd788e180562533babe8a8c76fbfd599 [path history] [tgz]
  1. android_compile.expected/
  2. bookmaker.expected/
  3. calmbench.expected/
  4. check_generated_files.expected/
  5. compile.expected/
  6. ct_skps.expected/
  7. housekeeper.expected/
  8. infra.expected/
  9. perf.expected/
  10. recreate_skps.expected/
  11. skpbench.expected/
  12. skqp_test.expected/
  13. test.expected/
  14. upload_calmbench_results.expected/
  15. upload_coverage_results.expected/
  16. upload_dm_results.expected/
  17. upload_nano_results.expected/
  18. upload_skiaserve.expected/
  19. android_compile.py
  20. bookmaker.py
  21. calmbench.py
  22. check_generated_files.py
  23. compile.py
  24. ct_skps.py
  25. housekeeper.py
  26. infra.py
  27. perf.py
  28. README.md
  29. recreate_skps.py
  30. skpbench.py
  31. skqp_test.py
  32. test.py
  33. upload_calmbench_results.py
  34. upload_coverage_results.py
  35. upload_dm_results.py
  36. upload_nano_results.py
  37. upload_skiaserve.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.