68e470de86
Also, create and use new service account for the G3 compile bots. Interesting failure here refers to when the bot fails only because of test failures and not: * merge failures * unknown failure reasons (eg: some flaky timeouts from the script running in borg) * when the bot is not owned or approved by a Googler NoTry: true Bug: skia:9631 Change-Id: I964fd7874269116cca0e25d1b516283a00d5133f Reviewed-on: https://skia-review.googlesource.com/c/skia/+/254278 Commit-Queue: Ravi Mistry <rmistry@google.com> Reviewed-by: Eric Boren <borenet@google.com>
25 lines
541 B
JSON
25 lines
541 B
JSON
[
|
|
{
|
|
"cmd": [
|
|
"python",
|
|
"[START_DIR]/skia/infra/bots/g3_compile/trigger_wait_g3_task.py",
|
|
"--issue",
|
|
"456789",
|
|
"--patchset",
|
|
"12",
|
|
"--output_file",
|
|
"[CLEANUP]/g3_try_tmp_1/output_file",
|
|
"--builder_name",
|
|
"Build-Debian9-Clang-TAP-Presubmit-G3_Framework"
|
|
],
|
|
"cwd": "[START_DIR]/skia",
|
|
"env": {
|
|
"CHROME_HEADLESS": "1",
|
|
"PATH": "<PATH>:RECIPE_REPO[depot_tools]"
|
|
},
|
|
"name": "Trigger and wait for g3 compile task"
|
|
},
|
|
{
|
|
"name": "$result"
|
|
}
|
|
] |