Show non-Blink ranges in sheriff-o-matic.

Show non-Blink ranges in sheriff-o-matic.

Show regression ranges for chromium/nacl/v8. Make CTCommitLog contain
a map of repository to commits and a map of repository to the first
revision the CTCommitLog has. Switch over to querying the data as JSON
from googlesource instead of XML from blink.lc.

Pass a map of repository -> revision for ct-commit-list's first
and last attributes and have ct-commit-list call out to CTCommitLog
to get the list of commits instead of generating them itself. If we
don't have data for a commit, create an incomplete CTCommit so that
we at least show the  repository + revision number instead of showing
nothing. This is for when the commits in the regression range are older
than the default number that googlesource's log shows.

We don't create an incomplete commit for revisions we don't have data
for that are after the first commit we have data for because those are
the commits that are on branches, which we don't want to show.

Also, delete unused ct-failure-grouper. I can move this into a separate patch if you'd like.

NOTRY=true

[ojan, 2014-07-25 01:38:58]

This depends on https://codereview.chromium.org/416673003.

After this, we just need to show information for different waterfalls and we'll
have a dogfoodable frontend. Once the backend issues with flaky tests are fixed,
then we can actually dogfood it.

[abarth-chromium, 2014-07-29 16:22:26]

LGTM

https://codereview.chromium.org/413073004/diff/40001/Tools/GardeningServer/mo...
File Tools/GardeningServer/model/ct-commit-log.html (right):

https://codereview.chromium.org/413073004/diff/40001/Tools/GardeningServer/mo...
Tools/GardeningServer/model/ct-commit-log.html:20:
Object.keys(this._repositories.repositories, (function(name, repository) {
repositories, repositories, repositories, repositories

https://codereview.chromium.org/413073004/diff/40001/Tools/GardeningServer/mo...
Tools/GardeningServer/model/ct-commit-log.html:33: json =
json.substring(')]}\n'.length);
Can we do a feature detect so that this code doesn't break when googlesource
removes the XSS mitigation?

https://codereview.chromium.org/413073004/diff/40001/Tools/GardeningServer/ui...
File Tools/GardeningServer/ui/ct-commit-list.html (right):

https://codereview.chromium.org/413073004/diff/40001/Tools/GardeningServer/ui...
Tools/GardeningServer/ui/ct-commit-list.html:17: <template repeat="{{ commit in
repository | _commits }}">
Do we want any sort of visual separation between commits in different repos?

[ojan, 2014-07-30 04:14:33]

https://codereview.chromium.org/413073004/diff/40001/Tools/GardeningServer/mo...
File Tools/GardeningServer/model/ct-commit-log.html (right):

https://codereview.chromium.org/413073004/diff/40001/Tools/GardeningServer/mo...
Tools/GardeningServer/model/ct-commit-log.html:20:
Object.keys(this._repositories.repositories, (function(name, repository) {
On 2014/07/29 16:22:26, abarth wrote:
> repositories, repositories, repositories, repositories

Yup. Felt silly writing this code, but didn't have an immediate idea of how to
make it better and wasn't too worried since it's not like it's spread out
throughout the codebase.

https://codereview.chromium.org/413073004/diff/40001/Tools/GardeningServer/mo...
Tools/GardeningServer/model/ct-commit-log.html:33: json =
json.substring(')]}\n'.length);
On 2014/07/29 16:22:26, abarth wrote:
> Can we do a feature detect so that this code doesn't break when googlesource
> removes the XSS mitigation?

Good idea. Done.

https://codereview.chromium.org/413073004/diff/40001/Tools/GardeningServer/ui...
File Tools/GardeningServer/ui/ct-commit-list.html (right):

https://codereview.chromium.org/413073004/diff/40001/Tools/GardeningServer/ui...
Tools/GardeningServer/ui/ct-commit-list.html:17: <template repeat="{{ commit in
repository | _commits }}">
On 2014/07/29 16:22:26, abarth wrote:
> Do we want any sort of visual separation between commits in different repos?

Probably. I was punting on making the UI nice for a followup patch.

What I think we really want though is that the the list of commits for each repo
is collapsed by default, e.g. you'd see:
Blink 1234:1235
Chromium 333:345

And you could click on it for the range to expand.

[ojan, 2014-07-30 05:04:11]

Whoops. I accidentally committed this as part of
https://codereview.chromium.org/418253002.