Sheriff-o-matic: Display snoozed failure groups in a separate stream

Tools/GardeningServer/ui/ct-failure-stream.html

Index: Tools/GardeningServer/ui/ct-failure-stream.html
diff --git a/Tools/GardeningServer/ui/ct-failure-stream.html b/Tools/GardeningServer/ui/ct-failure-stream.html
index a3412be0626816c3c76ccc9c4a970fa743ac2576..bf5619d9783392012668418aee0ac85fc3cddfc5 100644
--- a/Tools/GardeningServer/ui/ct-failure-stream.html
+++ b/Tools/GardeningServer/ui/ct-failure-stream.html
@@ -6,7 +6,7 @@ found in the LICENSE file.
 
 <link rel="import" href="ct-failure-card.html">
 
-<polymer-element name="ct-failure-stream" attributes="groups commits tree" noscript>
+<polymer-element name="ct-failure-stream" attributes="groups commits tree category" noscript>
   <template>
     <style>
       :host {
@@ -19,8 +19,11 @@ found in the LICENSE file.
         border-top: 1px solid lightgrey;
       }
     </style>
+    <!-- FIXME: Show a label based on the category when the filtered stream isn't empty -->
     <template repeat="{{ group in groups }}">
-      <ct-failure-card group="{{ group }}" commits="{{ commits }}" tree="{{ tree }}"></ct-failure-card>
+      <template if="{{ group.category == category }}">
+        <ct-failure-card group="{{ group }}" commits="{{ commits }}" tree="{{ tree }}"></ct-failure-card>

[ojan, 2014/08/11 03:43:35]

Can you also add ct-failure-stream tests? Just something basic that verifies
that you do/don't get ct-failure-cards in the right cases. Or, if you end up
making the change I'm requesting below, then you wouldn't be modifying this
file, but would need ct-unexpected-failures tests, which I'd be willing to leave
as a FIXME on until crbug.com/400394 is resolved since it's hard to mock out
ct-failure-analyzer.

+      </template>
     </template>
   </template>
 </polymer-element>