tree: fd52917733f0fc2a16e1e8afe2cd75cff2f8f364 [path history] [tgz]
  1. check_generated_files.expected/
  2. compile.expected/
  3. compute_buildstats.expected/
  4. housekeeper.expected/
  5. infra.expected/
  6. perf.expected/
  7. perf_pathkit.expected/
  8. perf_skottietrace.expected/
  9. perf_skottiewasm_lottieweb.expected/
  10. recreate_skps.expected/
  11. skpbench.expected/
  12. sync_and_compile.expected/
  13. test.expected/
  14. test_canvaskit.expected/
  15. test_lottie_web.expected/
  16. test_pathkit.expected/
  17. upload_buildstats_results.expected/
  18. upload_dm_results.expected/
  19. upload_nano_results.expected/
  20. check_generated_files.py
  21. compile.py
  22. compute_buildstats.py
  23. housekeeper.py
  24. infra.py
  25. perf.py
  26. perf_pathkit.py
  27. perf_skottietrace.py
  28. perf_skottiewasm_lottieweb.py
  29. README.md
  30. recreate_skps.py
  31. skpbench.py
  32. sync_and_compile.py
  33. test.py
  34. test_canvaskit.py
  35. test_lottie_web.py
  36. test_pathkit.py
  37. upload_buildstats_results.py
  38. upload_dm_results.py
  39. 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 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.