Polymer-based Garden-O-Matic should have a basic results panel

Tools/GardeningServer/ui/ct-failure-card.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="ct-commit-list.html">
+<link rel="import" href="ct-test-list.html">
+
+<polymer-element name="ct-failure-card" attributes="failures">
+  <template>
+    <style>
+      :host {
+        display: block;
+        margin: 5px;
+        padding: 5px;
+        border-top: 1px solid lightgrey;
+        min-height: 30px;
+      }
+
+      :host(:hover) > #examine {
+        display: initial;
+      }
+
+      #examine {
+        display: none;
+        float: right;
+      }
+
+      paper-button {
+        background: #4285f4;
+        color: #fff;
+      }
+    </style>
+    <paper-button id="examine" on-tap="{{examine}}">Examine</paper-button>
+    <ct-test-list tests="{{failures|testNames}}"></ct-test-list>
+    <ct-commit-list first="{{failures[0].newestPassingRevision + 1}}"
+                    last="{{failures[0].oldestFailingRevision}}"></ct-commits>

[michaelpg, 2014/06/29 23:16:05]

</ct-commit-list>

[michaelpg, 2014/06/29 23:58:32]

first and last are reversed (or, they need to be reversed in
ct-commit-data.html::update_()) - this passes an invalid revision range to the
model which is why no CLs are showing up, at least for me (Do the tests pass
with this?)

[abarth-chromium, 2014/06/30 00:43:28]

Why are they reversed?  The first (earliest) commit we want to show is the one
just after the last known passing revision and the last (latest) commit we want
to see is the oldest known failing revision:

ppppffffffffffff
 ^    ^

Where "p" means pass, "f" means fail, and the ^ indicate revisions that we have
observations about.  The commits we want to display start with the one to the
right of the first ^ and stop at the second ^.  The revision that caused the
failure is included in that range.

[michaelpg, 2014/06/30 02:32:38]

Sorry, you're totally right. What I was actually seeing was just
newestPassingRevision == oldestFailingRevision so that's why no CLs were
grabbed.

+  </template>
+  <script>
+    Polymer({
+      testNames: function(failures) {
+        return failures.map(function(failureAnalysis) { return failureAnalysis.testName });
+      },
+      examine: function() {
+        this.fire('ct-examine-failures', this.failures);
+      },
+    });
+  </script>
+</polymer-element>