f1215a537f
Turns out it's pretty easy to pass the compile outputs to the test task by just adding the hash to the "includes" list in the .isolated file. So the flow is: 1. Isolate skia repo 2. Run compile task, record hash of results 3. Isolate test inputs for DM. This writes a .isolated file 4. Edit the .isolated file from #3 to include the hash from #2 5. Upload the modified .isolated file to the isolate server 6. Trigger the swarming task for DM 7. Wait for DM task to finish, download results from isolate server 8. Upload results to GS as normal I expect the swarming bots to break when this is committed due to the moved out directory. The associated recipe change will fix them. NOTRY=true BUG=skia:4763 GOLD_TRYBOT_URL= https://gold.skia.org/search2?unt=true&query=source_type%3Dgm&master=false&issue=1759553003 Review URL: https://codereview.chromium.org/1759553003 |
||
|---|---|---|
| .. | ||
| bots | ||
| branch-config | ||
| project-config | ||
| OWNERS | ||
| README.md | ||
This directory contains infra-specific files. The branch-config/ directory contains configs that are specific to the master branch (e.g. config for the CQ committing to the master branch), while project-config/ directory contains project-wide configuration (e.g. list of buckets for cr-buildbucket service and list of refs known to the infra services).