|
Name |
|
Date |
Size |
#Lines |
LOC |
| .. | | - | - |
| builder_name_schema/ | | 03-May-2024 | - | 301 | 224 |
| core/ | | 03-May-2024 | - | 2,628 | 2,193 |
| ct/ | | 03-May-2024 | - | 383 | 350 |
| env/ | | 03-May-2024 | - | 102 | 73 |
| flavor/ | | 03-May-2024 | - | 25,385 | 24,830 |
| git/ | | 03-May-2024 | - | 74 | 48 |
| gsutil/ | | 03-May-2024 | - | 249 | 218 |
| infra/ | | 03-May-2024 | - | 614 | 563 |
| isolate/ | | 03-May-2024 | - | 2,945 | 2,726 |
| run/ | | 03-May-2024 | - | 594 | 536 |
| skia_swarming/ | | 03-May-2024 | - | 1,213 | 1,164 |
| swarming/ | | 03-May-2024 | - | 4,741 | 4,222 |
| swarming_client/ | | 03-May-2024 | - | 342 | 267 |
| vars/ | | 03-May-2024 | - | 807 | 727 |
| README.md | D | 03-May-2024 | 1.4 KiB | 36 | 27 |
README.md
1Skia Recipe Modules
2===================
3
4This directory contains recipe modules designed to be used by recipes (see
5infra/bots/recipes). They are all Skia-specific and some are interrelated:
6
7 * builder_name_schema - Helps to derive expected behavior from task (formerly
8 builder) names.
9 * core - Use as a starting point for most recipes: runs setup and sync steps.
10 * ct - Shared Cluster Telemetry utilities.
11 * flavor - Allows the caller to specify a high-level command to run, leaving
12 the platform-specific details to be handled by the specific flavor
13 module.
14 * infra - Shared infrastructure-related utilities.
15 * run - Utilities for running commands.
16 * swarming - Utilities for running Swarming tasks.
17 * vars - Common global variables used by Skia recipes/modules.
18
19When you change a recipe module, you generally need to re-train the simulation
20test:
21
22 $ python infra/bots/recipes.py test run --train
23
24Or:
25
26 $ cd infra/bots; make train
27
28Each recipe module contains a few files:
29
30 * api.py - This is the meat of the module.
31 * \_\_init\_\_.py - Contains a single DEPS variable, indicating the other
32 recipe modules on which this module depends.
33 * example.py - Optional, this file contains examples which demonstrate how to
34 use the module and should contain enough tests to achieve 100% coverage
35 for the module. The tests are run using the recipes test command above.
36