Get sheriff-o-matic data from auto-sheriff.appspot.com.

Tools/GardeningServer/ui/ct-unexpected-failures.html

 <!--
 Copyright 2014 The Chromium Authors. All rights reserved.
 Use of this source code is governed by a BSD-style license that can be
 found in the LICENSE file.
 -->
 
 <link rel="import" href="../bower_components/paper-button/paper-button.html">
-<link rel="import" href="../bower_components/paper-toast/paper-toast.html">
 <link rel="import" href="../model/ct-commit-log.html">
 <link rel="import" href="ct-failing-builders.html">
 <link rel="import" href="ct-failure-analyzer.html">
 <link rel="import" href="ct-failure-grouper.html">
 <link rel="import" href="ct-failure-stream.html">
 <link rel="import" href="ct-tree-status.html">
 
 <polymer-element name="ct-unexpected-failures">
   <template>
     <style>
-      paper-toast {
-        bottom: 40px;
-        left: 10px;
-      }
-
       ct-tree-status, ct-failing-builders {
         margin: 5px;
       }
     </style>
-    <ct-failure-analyzer id="analyzer" status="{{ analyzerStatus }}" failures="{{ failures }}" builderLatestRevisions="{{ builderLatestRevisions }}"></ct-failure-analyzer>
-    <ct-failure-grouper failures="{{ failures.unexpected }}" groups="{{ failureGroups }}"></ct-failure-grouper>

[ojan, 2014/07/21 00:44:57]

The grouping happens on the backend now, so no need for a dedicated grouper.

[abarth-chromium, 2014/07/21 06:44:18]

Neat

+    <ct-failure-analyzer id="analyzer" failures="{{ failures }}" builderLatestRevisions="{{ builderLatestRevisions }}"></ct-failure-analyzer>
     <ct-tree-status project="chromium"></ct-tree-status>
     <ct-tree-status project="blink"></ct-tree-status>
     <ct-failing-builders builders="{{ failures.builders }}"></ct-failing-builders>
-    <ct-failure-stream groups="{{ failureGroups }}" builderLatestRevisions="{{ builderLatestRevisions }}" commits="{{revisionLog.commits}}"></ct-failure-stream>
-    <paper-toast id="toast" text="{{ analyzerStatus }}"></paper-toast>

[ojan, 2014/07/21 00:44:57]

No more need for a toast anymore since we load so quickly.

+    <ct-failure-stream groups="{{ failures.unexpected }}" builderLatestRevisions="{{ builderLatestRevisions }}" commits="{{revisionLog.commits}}"></ct-failure-stream>
   </template>
   <script>
     Polymer({
       revisionLog: new CTCommitLog(),
 
       attached: function() {
         this.update();
         setInterval(this.update.bind(this), config.kUpdateFrequency);
       },
 
       update: function() {
         // FIXME: These shouldn't update if there's already an update in progress.
         this.revisionLog.update();
         this.$.analyzer.update();
         var treeStatuses = this.shadowRoot.querySelectorAll("ct-tree-status");
         for (var i = 0; i < treeStatuses.length; i++)
           treeStatuses[i].update();
       },
-
-      analyzerStatusChanged: function() {
-        this.$.toast.show();
-      },
     });
   </script>
 </polymer-element>