1d766830ba
This can take a few minutes, a fair chunk of some runs. E.g. https://ci.chromium.org/raw/build/logs.chromium.org/skia/51ee56ccc7f9ba11/+/annotations debugging 2m32s (17%) + dm 11m17s (77%) + other 54s ( 6%) = total 14m43s should become more like dm 11m17s (93%) + other 54s ( 7%) = total 12m11s Change-Id: I8bdbc280f5d581d98b08e471613401eee507064e Reviewed-on: https://skia-review.googlesource.com/c/skia/+/375184 Reviewed-by: Eric Boren <borenet@google.com> Commit-Queue: Mike Klein <mtklein@google.com> |
||
|---|---|---|
| .. | ||
| check_generated_files.expected | ||
| compile.expected | ||
| compute_buildstats.expected | ||
| compute_test.expected | ||
| housekeeper.expected | ||
| infra.expected | ||
| perf_canvaskit.expected | ||
| perf_pathkit.expected | ||
| perf_skottietrace.expected | ||
| perf_skottiewasm_lottieweb.expected | ||
| perf.expected | ||
| recreate_skps.expected | ||
| skpbench.expected | ||
| sync_and_compile.expected | ||
| test_canvaskit.expected | ||
| test_lottie_web.expected | ||
| test_pathkit.expected | ||
| test_skqp_emulator.expected | ||
| test.expected | ||
| upload_buildstats_results.expected | ||
| upload_dm_results.expected | ||
| upload_nano_results.expected | ||
| check_generated_files.py | ||
| compile.py | ||
| compute_buildstats.py | ||
| compute_test.py | ||
| housekeeper.py | ||
| infra.py | ||
| perf_canvaskit.py | ||
| perf_pathkit.py | ||
| perf_skottietrace.py | ||
| perf_skottiewasm_lottieweb.py | ||
| perf.py | ||
| README.md | ||
| recreate_skps.py | ||
| skpbench.py | ||
| sync_and_compile.py | ||
| test_canvaskit.py | ||
| test_lottie_web.py | ||
| test_pathkit.py | ||
| test_skqp_emulator.py | ||
| test.py | ||
| upload_buildstats_results.py | ||
| upload_dm_results.py | ||
| upload_nano_results.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.