AuroraMiddleware/skia2
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
587afc9df0
skia2/infra/bots/recipes
History
Kevin Lubick 587afc9df0 Update to adb 1.0.35 
The newer adb acts more like cp when pulling. We used to 
create the dm folder on the host machine before pulling.

This used to be fine, 
/device/dm_out/dm.json -> /host/dm/dm.json

However, with the update, adb would do
/device/dm_out/dm.json -> /host/dm/dm_out/dm.json

This breaks the upload step.  To make this transition
a smooth one, /usr/bin/adb on the RPI is staying the same
(for a while, at least) and /usr/bin/adb.1.0.35 is being added.

That way we can use the new adb on tests after this commit, but
when we backfill, we don't break because of the unexpected folder.

Bug: skia:
Change-Id: Icbed38594fca0e17af1f8d01d75c42ce03f710b9
Reviewed-on: https://skia-review.googlesource.com/58880
Commit-Queue: Kevin Lubick <kjlubick@google.com>
Reviewed-by: Eric Boren <borenet@google.com>
2017-10-12 17:22:12 +00:00
..
bundle_recipes.expected Use chrome-infra Git CIPD package 2017-06-06 12:45:11 +00:00
check_generated_files.expected [infra] Bring recipe DEPS up to date 2017-09-22 20:05:38 +00:00
compile.expected Switch most Win Vulkan jobs to Clang. 2017-10-11 15:00:10 +00:00
ct_skps.expected Manually roll recipe DEPS 2017-09-27 17:24:38 +00:00
housekeeper.expected [infra] Bring recipe DEPS up to date 2017-09-22 20:05:38 +00:00
infra.expected [infra] Bring recipe DEPS up to date 2017-09-22 20:05:38 +00:00
perf.expected Update to adb 1.0.35 2017-10-12 17:22:12 +00:00
recreate_skps.expected Make ct_skps and recreate_skps recipes shell to gsutil 2017-09-25 13:53:53 +00:00
skpbench.expected Update to adb 1.0.35 2017-10-12 17:22:12 +00:00
test.expected Update to adb 1.0.35 2017-10-12 17:22:12 +00:00
update_meta_config.expected [infra] Bring recipe DEPS up to date 2017-09-22 20:05:38 +00:00
upload_coverage_results.expected Add Linux CPU Coverage Bot 2017-10-09 19:58:34 +00:00
upload_dm_results.expected [recipes] Update example builder names. 2017-09-26 20:26:56 +00:00
upload_nano_results.expected [recipes] Update example builder names. 2017-09-26 20:26:56 +00:00
bundle_recipes.py Use chrome-infra Git CIPD package 2017-06-06 12:45:11 +00:00
check_generated_files.py Add a bot to verify that generated SKSL files have not been hand-edited 2017-07-28 12:20:47 +00:00
compile.py Switch most Win Vulkan jobs to Clang. 2017-10-11 15:00:10 +00:00
ct_skps.py Specify CPU for CT Swarming tasks. 2017-09-25 19:48:49 +00:00
housekeeper.py [skia] convert recipes and module to new context module 2017-05-15 13:46:22 +00:00
infra.py Fixes for internal repo infra tests 2017-06-15 13:10:59 +00:00
perf.py Update to adb 1.0.35 2017-10-12 17:22:12 +00:00
README.md Use new recipes.py test command 2017-04-18 13:57:56 +00:00
recreate_skps.py Make ct_skps and recreate_skps recipes shell to gsutil 2017-09-25 13:53:53 +00:00
skpbench.py Remove dependency on recipe_engine/shutil. 2017-07-10 13:46:35 +00:00
test.py Update to adb 1.0.35 2017-10-12 17:22:12 +00:00
update_meta_config.py [recipes] Switch to file module from recipe_engine 2017-06-16 17:41:28 +00:00
upload_coverage_results.py Add Linux CPU Coverage Bot 2017-10-09 19:58:34 +00:00
upload_dm_results.py Add Linux CPU Coverage Bot 2017-10-09 19:58:34 +00:00
upload_nano_results.py [recipes] Update example builder names. 2017-09-26 20:26:56 +00:00

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.