master.chromium.perf.fyi: order console by time

master.chromium.perf.fyi: order console by time

gitiles revision comparator assumes that all rows in the changes table 
were created by it, which is not the case with buildbucket, so we are 
switching to a more generic comparator 

there is a possibility that it may cause some weird presentation of 
console view, in particular some rows in the console view may look like

rev deadbeef
rev badcoffee
rev deadbeef

because changes created by buidlbucket module have timestamp equal 
to the build creation time

R=dnj@chromium.org
BUG=626019
Committed: https://chromium.googlesource.com/chromium/tools/build/+/5ff472dc7cd21a25d968e4a7d901000bee38304e

[nodir, 2016-07-15 18:59:57]

PTAL

[dnj (Google), 2016-07-15 19:00:20]

dnj@google.com changed reviewers:
+ dnj@google.com

[dnj (Google), 2016-07-15 19:00:21]

The CQ bit was checked by dnj@google.com

[dnj (Google), 2016-07-15 19:00:21]

lgtm

[commit-bot: I haz the power, 2016-07-15 19:00:24]

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

[nodir, 2016-07-15 19:01:44]

Description was changed from

==========
master.chromium.perf.fyi: order console by time

R=dnj@chromium.org
BUG=626019
==========

to

==========
master.chromium.perf.fyi: order console by time

gitiles revision comparator assumes that all rows in the changes table were
created by it, which is not the case with buildbucket, so we are switching to a
more generic comparator 

R=dnj@chromium.org
BUG=626019
==========

[nodir, 2016-07-15 19:03:26]

Description was changed from

==========
master.chromium.perf.fyi: order console by time

gitiles revision comparator assumes that all rows in the changes table were
created by it, which is not the case with buildbucket, so we are switching to a
more generic comparator 

R=dnj@chromium.org
BUG=626019
==========

to

==========
master.chromium.perf.fyi: order console by time

gitiles revision comparator assumes that all rows in the changes table 
were created by it, which is not the case with buildbucket, so we are 
switching to a more generic comparator 

there is a possibility that it may cause some weird presentation of console
view, in particular some rows in the console view may look like

rev deadbeef
rev badcoffee
rev deadbeef

because changes created by buidlbucket module have timestamp equal to the build
creation time

R=dnj@chromium.org
BUG=626019
==========

[nodir, 2016-07-15 19:03:38]

Description was changed from

==========
master.chromium.perf.fyi: order console by time

gitiles revision comparator assumes that all rows in the changes table 
were created by it, which is not the case with buildbucket, so we are 
switching to a more generic comparator 

there is a possibility that it may cause some weird presentation of console
view, in particular some rows in the console view may look like

rev deadbeef
rev badcoffee
rev deadbeef

because changes created by buidlbucket module have timestamp equal to the build
creation time

R=dnj@chromium.org
BUG=626019
==========

to

==========
master.chromium.perf.fyi: order console by time

gitiles revision comparator assumes that all rows in the changes table 
were created by it, which is not the case with buildbucket, so we are 
switching to a more generic comparator 

there is a possibility that it may cause some weird presentation of 
console view, in particular some rows in the console view may look like

rev deadbeef
rev badcoffee
rev deadbeef

because changes created by buidlbucket module have timestamp equal 
to the build creation time

R=dnj@chromium.org
BUG=626019
==========

[commit-bot: I haz the power, 2016-07-15 19:04:13]

Description was changed from

==========
master.chromium.perf.fyi: order console by time

gitiles revision comparator assumes that all rows in the changes table 
were created by it, which is not the case with buildbucket, so we are 
switching to a more generic comparator 

there is a possibility that it may cause some weird presentation of 
console view, in particular some rows in the console view may look like

rev deadbeef
rev badcoffee
rev deadbeef

because changes created by buidlbucket module have timestamp equal 
to the build creation time

R=dnj@chromium.org
BUG=626019
==========

to

==========
master.chromium.perf.fyi: order console by time

gitiles revision comparator assumes that all rows in the changes table 
were created by it, which is not the case with buildbucket, so we are 
switching to a more generic comparator 

there is a possibility that it may cause some weird presentation of 
console view, in particular some rows in the console view may look like

rev deadbeef
rev badcoffee
rev deadbeef

because changes created by buidlbucket module have timestamp equal 
to the build creation time

R=dnj@chromium.org
BUG=626019

Committed:
https://chromium.googlesource.com/chromium/tools/build/+/5ff472dc7cd21a25d968...
==========

[commit-bot: I haz the power, 2016-07-15 19:04:14]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/tools/build/+/5ff472dc7cd21a25d968...

[nodir, 2016-07-16 00:57:43]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/2154043002/ by nodir@chromium.org.

The reason for reverting is: reverting in favor of
https://codereview.chromium.org/2157703002.