Chromium Code Reviews| Index: appengine/findit/waterfall/trigger_swarming_task_pipeline.py |
| diff --git a/appengine/findit/waterfall/trigger_swarming_task_pipeline.py b/appengine/findit/waterfall/trigger_swarming_task_pipeline.py |
| index 63c4393bdeb33bd566f1235169677e787ecc253a..b82c0da10e69ac6a4cf863a39defaa4c9ca0aa27 100644 |
| --- a/appengine/findit/waterfall/trigger_swarming_task_pipeline.py |
| +++ b/appengine/findit/waterfall/trigger_swarming_task_pipeline.py |
| @@ -54,6 +54,7 @@ def _CreateNewSwarmingTaskRequest( |
| ] |
| # Reset tags for searching and monitoring. |
| + ref_name = swarming_util.GetTagValue(new_request.tags, 'name') or step_name |
|
stgao
2016/03/10 23:50:28
Should get from the `ref_request` instead, right?
stgao
2016/03/10 23:50:28
And should not default to the step_name.
stgao
2016/03/10 23:50:28
I'm wondering why don't we get the name from the c
chanli
2016/03/11 00:49:41
No, this is the referred task, the tag is 'name',
chanli
2016/03/11 00:49:41
Done.
chanli
2016/03/11 00:49:41
If we get the name when we list swarming tasks in
stgao
2016/03/11 01:03:20
My thought is that ref_request is the original dat
chanli
2016/03/11 03:47:00
But before you clear new_request.tags, the tags in
stgao
2016/03/11 06:42:58
Using either new_request.tags or ref_request.tags
|
| new_request.tags = [] |
| new_request.tags.append('purpose:deflake') |
| new_request.tags.append('ref_master:%s' % master_name) |
| @@ -61,6 +62,7 @@ def _CreateNewSwarmingTaskRequest( |
| new_request.tags.append('ref_buildnumber:%s' % build_number) |
| new_request.tags.append('ref_stepname:%s' % step_name) |
| new_request.tags.append('ref_task_id:%s' % ref_task_id) |
| + new_request.tags.append('ref_name:%s' % ref_name) |
| return new_request |