044044f5a2
The old win_toolchain script required a Chromium checkout, and extracted portions of the win_toolchain from that to build the Skia asset. Instead, use the depot_tools script that assembles a toolchain from a locally installed MSVC. The create script doesn't do that, but relies on the user to run that script first. Automating everything would be a nice follow-up. With the new strategy, the toolchain directory is simpler, and no longer contains the depot_tools kruft or extra directories. Adjust the bot scripts accordingly. (Renaming the directory to win_toolchain from 't' would be a nice touch, too). Finally, I built the new toolchain with the updated process, and included the ARM64 compiler and libraries, so we can set up a bot to build Windows ARM64. Docs-Preview: https://skia.org/?cl=176968 Bug: skia:8569 Change-Id: I4bdf3cfb29d50f4464853445d0226241e70c33b4 Reviewed-on: https://skia-review.googlesource.com/c/176968 Reviewed-by: Mike Klein <mtklein@google.com> Reviewed-by: Eric Boren <borenet@google.com> Commit-Queue: Brian Osman <brianosman@google.com> |
||
|---|---|---|
| .. | ||
| android_compile.expected | ||
| bookmaker.expected | ||
| calmbench.expected | ||
| check_generated_files.expected | ||
| compile.expected | ||
| compute_buildstats.expected | ||
| compute_test.expected | ||
| housekeeper.expected | ||
| infra.expected | ||
| perf_canvaskit.expected | ||
| perf_pathkit.expected | ||
| perf.expected | ||
| recreate_skps.expected | ||
| skpbench.expected | ||
| skqp_test.expected | ||
| test_canvaskit.expected | ||
| test_lottie_web.expected | ||
| test_pathkit.expected | ||
| test_skqp_emulator.expected | ||
| test.expected | ||
| update_go_deps.expected | ||
| upload_buildstats_results.expected | ||
| upload_calmbench_results.expected | ||
| upload_dm_results.expected | ||
| upload_nano_results.expected | ||
| upload_skiaserve.expected | ||
| android_compile.py | ||
| bookmaker.py | ||
| calmbench.py | ||
| check_generated_files.py | ||
| compile.py | ||
| compute_buildstats.py | ||
| compute_test.py | ||
| housekeeper.py | ||
| infra.py | ||
| perf_canvaskit.py | ||
| perf_pathkit.py | ||
| perf.py | ||
| README.md | ||
| recreate_skps.py | ||
| skpbench.py | ||
| skqp_test.py | ||
| test_canvaskit.py | ||
| test_lottie_web.py | ||
| test_pathkit.py | ||
| test_skqp_emulator.py | ||
| test.py | ||
| update_go_deps.py | ||
| upload_buildstats_results.py | ||
| upload_calmbench_results.py | ||
| upload_dm_results.py | ||
| upload_nano_results.py | ||
| upload_skiaserve.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.