965451ed83
This helps the linker decide to rewrite bl -> blx when linking Thumb2 SkJumper.o code with ARM SkJumper_generated.o. The reason Android wasn't failing is because it somehow figured out to do this without these .type directives. We use a different toolchain for ChromeOS builds that I guess needs more handholding. BUG=skia:6471 CQ_INCLUDE_TRYBOTS=skia.primary:Test-ChromeOS-Clang-Chromebook_C100p-GPU-MaliT764-arm-Release,Test-ChromeOS-Clang-Chromebook_C100p-GPU-MaliT764-arm-Debug Change-Id: I4a5c50b6ab7683512776c70aec6e9a75a0999787 Reviewed-on: https://skia-review.googlesource.com/13464 Reviewed-by: Herb Derby <herb@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org> |
||
---|---|---|
.. | ||
bundle_recipes.expected | ||
compile.expected | ||
ct_skps.expected | ||
housekeeper.expected | ||
infra.expected | ||
perf.expected | ||
recreate_skps.expected | ||
skpbench.expected | ||
test.expected | ||
upload_dm_results.expected | ||
upload_nano_results.expected | ||
bundle_recipes.py | ||
compile.py | ||
ct_skps.py | ||
housekeeper.py | ||
infra.py | ||
perf.py | ||
README.md | ||
recreate_skps.py | ||
skpbench.py | ||
test.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 simulation_test train
Or:
$ cd infra/bots; make train
The simulation_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.