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