1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
|
Skia Infrastructure
===================
This directory contains infrastructure elements.
Tasks and Jobs
--------------
Files in this directory define a DAG of tasks which run at every Skia commit. A
task is a small, self-contained unit which runs via Swarming on a machine in the
pool. Tasks may be chained together, eg. one task to compile test binaries and
another to actually run them.
Jobs are collections of related tasks which help define sub-sections of the DAG,
for example, to be used as try jobs. Each job is defined as an entry point into
the DAG.
The tasks.json file in this directory is the master list of tasks and jobs for
the repo. Note that tasks.json is NEVER edited by hand but generated via
gen_task.go and the input files enumerated below. The
[Task Scheduler](https://skia.googlesource.com/buildbot/+/master/task_scheduler/README.md)
reads the tasks.json file at each commit to determine which jobs to run. For
convenience, gen_tasks.go is provided to generate tasks.json and also to test it
for correct syntax and detecting cycles and orphaned tasks. Always edit
gen_tasks.go or one of the following input JSON files, rather than tasks.json
itself:
* android_map.json - Maps human-friendly names of Android devices to their
device codename and desired OS version. Edit this file when adding a new
type of Android device or updating the desired OS version.
* cfg.json - Basic configuration information for gen_tasks.go.
* gpu_map.json - Maps human-friendly names of GPUs to an appropriate Swarming
dimension, typically the PCI ID of the GPU. Edit this file when adding a
new GPU.
* jobs.json - The master list of all jobs to run. Edit this to add or remove
bots.
Whenever gen_tasks.go, any of the above JSON files, or assets are changed, you
need to run gen_tasks.go to regenerate tasks.json:
$ go run infra/bots/gen_tasks.go
Or:
$ cd infra/bots; make train
There is also a test mode which performs sanity-checks and verifies that
tasks.json is unchanged:
$ go run infra/bots/gen_tasks.go --test
Or:
$ cd infra/bots; make test
Recipes
-------
Recipes are the framework used by Skia's infrastructure to perform work inside
of Swarming tasks. The main elements are:
* recipes.py - Used for running and testing recipes.
* recipes - These are the entry points for each type of task, eg. compiling
or running tests.
* recipe_modules - Shared modules which are used by recipes.
* .recipe_deps - Recipes and modules may depend on modules from other repos.
The recipes.py script automatically syncs those dependencies in this
directory.
Isolate Files
-------------
These files determine which parts of the repository are transferred to the bot
when a Swarming task is triggered. The
[Isolate tool](https://github.com/luci/luci-py/tree/master/appengine/isolate/doc)
hashes each file and will upload any new/changed files. Bots maintain a cache so
that they can efficiently download only the files they don't have.
Assets
------
Artifacts used by the infrastructure are versioned here, along with scripts for
recreating/uploading/downloading them. See the README in that directory for more
information. Any time an asset used by the bots changes, you need to re-run
gen_tasks.go.
Tools
-----
Assorted other infrastructure-related tools, eg. isolate and CIPD binaries.
CT
--
Helpers for running Skia tasks in Cluster Telemetry.
|
