a2931beb4b
We've failed to get these bots to report where issues happen any more finely than the name of the executable, which makes them a real pain to fix when they go red. We don't expect we'll be able to run cleanly in this mode for long without bots enforcing it, so remove support from GN too. Change-Id: Ie86f0cbf2f5f859ac2ddb869da7e5b8d31b33fa0 Reviewed-on: https://skia-review.googlesource.com/c/skia/+/237195 Reviewed-by: Brian Osman <brianosman@google.com> Commit-Queue: Mike Klein <mtklein@google.com> |
||
|---|---|---|
| .. | ||
| build | ||
| builder_name_schema | ||
| checkout | ||
| doxygen | ||
| env | ||
| flavor | ||
| git | ||
| gsutil | ||
| infra | ||
| run | ||
| vars | ||
| README.md | ||
Skia Recipe Modules
This directory contains recipe modules designed to be used by recipes (see infra/bots/recipes). They are all Skia-specific and some are interrelated:
- builder_name_schema - Helps to derive expected behavior from task (formerly builder) names.
- core - Use as a starting point for most recipes: runs setup and sync steps.
- ct - Shared Cluster Telemetry utilities.
- flavor - Allows the caller to specify a high-level command to run, leaving the platform-specific details to be handled by the specific flavor module.
- infra - Shared infrastructure-related utilities.
- run - Utilities for running commands.
- swarming - Utilities for running Swarming tasks.
- vars - Common global variables used by Skia recipes/modules.
When you change a recipe module, you generally need to re-train the simulation test:
$ python infra/bots/recipes.py test run --train
Or:
$ cd infra/bots; make train
Each recipe module contains a few files:
- api.py - This is the meat of the module.
- __init__.py - Contains a single DEPS variable, indicating the other recipe modules on which this module depends.
- example.py - Optional, this file contains examples which demonstrate how to use the module and should contain enough tests to achieve 100% coverage for the module. The tests are run using the recipes test command above.