Add failed builders to sheriff-o-matic.

Tools/GardeningServer/ui/ct-builder.html

Index: Tools/GardeningServer/ui/ct-builder.html
diff --git a/Tools/GardeningServer/ui/ct-builder.html b/Tools/GardeningServer/ui/ct-builder.html
index 97cf7baa3493e338778c19224cac75e94c5ff933..4df13e4a8c186d97b91899ed4d835d87ac5e69bc 100644
--- a/Tools/GardeningServer/ui/ct-builder.html
+++ b/Tools/GardeningServer/ui/ct-builder.html
@@ -4,8 +4,12 @@ Use of this source code is governed by a BSD-style license that can be
 found in the LICENSE file.
 -->
 
-<!-- Styled link to a builder composed of the version and architecture. -->
-<polymer-element name="ct-builder" attributes="builderName">
+<!--
+Styled link to a builder composed of the version and architecture, or the
+builder name if the builder is unknown. If an array is passed to |steps|, the
+link will show the builder name and architecture followed by the steps instead.
+-->
+<polymer-element name="ct-builder" attributes="builderName steps">
   <template>
     <style>
       a {
@@ -26,27 +30,48 @@ found in the LICENSE file.
       .version {
         background-color: #555;
         color: white;
+      }
+
+      .version:not(.architecture) {
         text-transform: uppercase;
       }
+
+      .details {
+        padding-left: 3px;
+      }
     </style>
     <a href="{{ builderName|builderURL }}">
       <template if="{{ configuration }}">
         <span class="version">{{ configuration.version }}</span>
         <template if="{{ configuration.is64bit }}">
-          <span class="architecture">64-bit</span>
+          <template if="{{ stepList }}">
+            <span class="version architecture">64-bit</span>
+          </template>
+          <template if="{{ !stepList }}">
+            <span>64-bit</span>
+          </template>
         </template>
       </template>
       <template if="{{ !configuration }}">
         <span class="version">{{ builderName }}</span>
       </template>
+      <template if="{{ stepList }}">
+        <span class="details">{{ stepList }}</span>
+      </template>
     </a>
   </template>
   <script>
     Polymer({
+      steps: [],
+
       ready: function() {
         this.configuration = config.builders[this.builderName];
       },
 
+      stepsChanged: function() {
+        this.stepList = this.steps.join(', ');
+      },

[abarth-chromium, 2014/07/07 23:59:45]

The microtask checkpoint is a queue.  These lines of code add some more work to
the queue (i.e., to process that the stepList changed).  Your test code appears
to be running after this code has run but before the work it has queued runs. 
If you add another Platform.endOfMicrotask call, you'll go back to the end of
the queue and the system should have processed the change to the step list by
then.

[michaelpg, 2014/07/08 00:56:03]

Yes, this is exactly what's happening -- the template changes haven't been
performed yet.
 
Do you mean nest the call, or add them sequentially? Regardless, I've tried
adding a dozen calls and it doesn't help. Using el.async instead of
Platform.endOfMicrotask does work, though. :-\

+
       builderURL: function() {
          return config.waterfallURL + '?builder=' +
              encodeURIComponent(this.builderName);