Add script that triggers a task on CTFE and then waits for its completion or times out

Add script that triggers a task on CTFE and then waits for its completion or times out

This script will be called from a new CT trybot recipe.

BUG=skia:4341
NOTRY=true

Committed: https://skia.googlesource.com/buildbot/+/ceb90e2ffd04ab36a57c0db4b84d2258a4b4dd4a

[rmistry, 2015-09-24 18:11:50]

rmistry@google.com changed reviewers:
+ borenet@google.com

[borenet, 2015-09-24 18:42:46]

https://codereview.chromium.org/1370523002/diff/1/ct/py/trigger_wait_ct_task.py
File ct/py/trigger_wait_ct_task.py (right):

https://codereview.chromium.org/1370523002/diff/1/ct/py/trigger_wait_ct_task....
ct/py/trigger_wait_ct_task.py:41: task_params["page_sets"] = "10k"
Can we plumb the platform and page_sets parameters through so that we could
have, eg. a 1M trybot?

https://codereview.chromium.org/1370523002/diff/1/ct/py/trigger_wait_ct_task....
ct/py/trigger_wait_ct_task.py:152: help='The Rietveld CL number to get the patch
from.')
Looks like we're missing the patchset option?

[rmistry, 2015-09-24 18:51:19]

https://codereview.chromium.org/1370523002/diff/1/ct/py/trigger_wait_ct_task.py
File ct/py/trigger_wait_ct_task.py (right):

https://codereview.chromium.org/1370523002/diff/1/ct/py/trigger_wait_ct_task....
ct/py/trigger_wait_ct_task.py:41: task_params["page_sets"] = "10k"
On 2015/09/24 18:42:46, borenet wrote:
> Can we plumb the platform and page_sets parameters through so that we could
> have, eg. a 1M trybot?

Yes we could plumb different combinations of the params here. I was thinking of
starting simple initially and then going from there.
I initially envision a ct_rr_linux_trybot and ct_repaint_linux_trybot that uses
default values.

https://codereview.chromium.org/1370523002/diff/1/ct/py/trigger_wait_ct_task....
ct/py/trigger_wait_ct_task.py:152: help='The Rietveld CL number to get the patch
from.')
On 2015/09/24 18:42:46, borenet wrote:
> Looks like we're missing the patchset option?

I initially thought it would always use only the latest patchset but that does
not make sense if we only use one slave and there are pending builds waiting for
a long time. Multiple new patchsets could be added to the CL by then and it
could end up testing an unintended patchset. Done.

[borenet, 2015-09-24 18:53:21]

On 2015/09/24 18:51:19, rmistry wrote:
>
https://codereview.chromium.org/1370523002/diff/1/ct/py/trigger_wait_ct_task.py
> File ct/py/trigger_wait_ct_task.py (right):
> 
>
https://codereview.chromium.org/1370523002/diff/1/ct/py/trigger_wait_ct_task....
> ct/py/trigger_wait_ct_task.py:41: task_params["page_sets"] = "10k"
> On 2015/09/24 18:42:46, borenet wrote:
> > Can we plumb the platform and page_sets parameters through so that we could
> > have, eg. a 1M trybot?
> 
> Yes we could plumb different combinations of the params here. I was thinking
of
> starting simple initially and then going from there.
> I initially envision a ct_rr_linux_trybot and ct_repaint_linux_trybot that
uses
> default values.
> 
>
https://codereview.chromium.org/1370523002/diff/1/ct/py/trigger_wait_ct_task....
> ct/py/trigger_wait_ct_task.py:152: help='The Rietveld CL number to get the
patch
> from.')
> On 2015/09/24 18:42:46, borenet wrote:
> > Looks like we're missing the patchset option?
> 
> I initially thought it would always use only the latest patchset but that does
> not make sense if we only use one slave and there are pending builds waiting
for
> a long time. Multiple new patchsets could be added to the CL by then and it
> could end up testing an unintended patchset. Done.

LGTM

[rmistry, 2015-09-25 11:28:01]

The CQ bit was checked by rmistry@google.com

[commit-bot: I haz the power, 2015-09-25 11:28:06]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1370523002/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1370523002/20001

[commit-bot: I haz the power, 2015-09-25 11:30:45]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-09-25 11:30:46]

Try jobs failed on following builders:
  Infra-PerCommit-Trybot on client.skia.fyi (JOB_FAILED,
http://build.chromium.org/p/client.skia.fyi/builders/Infra-PerCommit-Trybot/b...)

[rmistry, 2015-09-25 11:34:06]

The CQ bit was checked by rmistry@google.com

[commit-bot: I haz the power, 2015-09-25 11:34:15]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1370523002/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1370523002/20001

[commit-bot: I haz the power, 2015-09-25 11:34:31]

Committed patchset #2 (id:20001) as
https://skia.googlesource.com/buildbot/+/ceb90e2ffd04ab36a57c0db4b84d2258a4b4...