[Sheriff-o-matic] Use likely_revisions instead of first_failing/last_passing

Tools/GardeningServer/model/ct-commit-list-mock.html

Index: Tools/GardeningServer/model/ct-commit-list-mock.html
diff --git a/Tools/GardeningServer/model/ct-commit-list-mock.html b/Tools/GardeningServer/model/ct-commit-list-mock.html
index a0b729f8e6a73527536bd39cdce7682b847a9475..b53f1a94224962402010c692eac8c1a0abc69e12 100644
--- a/Tools/GardeningServer/model/ct-commit-list-mock.html
+++ b/Tools/GardeningServer/model/ct-commit-list-mock.html
@@ -12,19 +12,8 @@ found in the LICENSE file.
 (function () {
 
 window.CTCommitListMock = function() {
-  var group = {
-    failures: [
-      {
-        firstFailingRevisions: {
-          'blink': 158545
-        },
-        lastPassingRevisions: {
-          'blink': 158544
-        }
-      }
-    ]
-  };
-  return new CTCommitList(group, new CTCommitLogMock());
+  var revisions = ['blink:158544', 'blink:158545'];
+  return new CTCommitList(new CTCommitLogMock(), revisions);
 };
 
 })();