When fetching try jobs for a CL, include only the latest for each builder.

When fetching try jobs for a CL, include only the latest for each builder.

This changes webkitpy.common.net.rietveld.latest_try_jobs to return only
the latest try job for each builder on the latest patchset; previously
it would return all try jobs for the latest patchset, even if there are
multiple retries for the same builder.

This is the behavior I believe we want for rebaselining from try jobs,
because if some flaky tests fail in a try job on one try, that builder
can be retried, and then new baselines should be downloaded only for
the latest run for that builder.

BUG=474273
Committed: https://crrev.com/a8fa41e4ad43d97dff7184069da9d169b3cd1aab
Cr-Commit-Position: refs/heads/master@{#405796}

[qyearsley, 2016-07-13 03:28:39]

qyearsley@chromium.org changed reviewers:
+ dpranke@chromium.org, raikiri@google.com, wkorman@chromium.org

[qyearsley, 2016-07-14 17:15:55]

The CQ bit was checked by qyearsley@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-07-14 17:16:04]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-07-14 18:42:35]

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

[commit-bot: I haz the power, 2016-07-14 18:42:36]

Dry run: This issue passed the CQ dry run.

[wkorman, 2016-07-15 00:19:21]

lgtm

[qyearsley, 2016-07-15 17:24:16]

The CQ bit was checked by qyearsley@chromium.org

[commit-bot: I haz the power, 2016-07-15 17:25:00]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-07-15 18:20:25]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-07-15 18:23:26]

Description was changed from

==========
When fetching try jobs for a CL, include only the latest for each builder.

This changes webkitpy.common.net.rietveld.latest_try_jobs to return only
the latest try job for each builder on the latest patchset; previously
it would return all try jobs for the latest patchset, even if there are
multiple retries for the same builder.

This is the behavior I believe we want for rebaselining from try jobs,
because if some flaky tests fail in a try job on one try, that builder
can be retried, and then new baselines should be downloaded only for
the latest run for that builder.

BUG=474273
==========

to

==========
When fetching try jobs for a CL, include only the latest for each builder.

This changes webkitpy.common.net.rietveld.latest_try_jobs to return only
the latest try job for each builder on the latest patchset; previously
it would return all try jobs for the latest patchset, even if there are
multiple retries for the same builder.

This is the behavior I believe we want for rebaselining from try jobs,
because if some flaky tests fail in a try job on one try, that builder
can be retried, and then new baselines should be downloaded only for
the latest run for that builder.

BUG=474273

Committed: https://crrev.com/a8fa41e4ad43d97dff7184069da9d169b3cd1aab
Cr-Commit-Position: refs/heads/master@{#405796}
==========

[commit-bot: I haz the power, 2016-07-15 18:23:27]

Patchset 1 (id:??) landed as
https://crrev.com/a8fa41e4ad43d97dff7184069da9d169b3cd1aab
Cr-Commit-Position: refs/heads/master@{#405796}

[Dirk Pranke, 2016-08-09 04:01:56]

lgtm (very belatedly).