[Findit] Adding suspected CL to master flake analysis in preparation for try jobs

appengine/findit/model/flake/flake_culprit.py

+# Copyright 2017 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.
+
+from google.appengine.ext import ndb
+
+from model.base_suspected_cl import BaseSuspectedCL
+
+
+class FlakeCulprit(BaseSuspectedCL):

[chanli, 2017/01/10 00:28:35]

What do you think if we use FlakeSuspectedCL?

[lijeffrey, 2017/01/10 01:16:25]

I originally called it that but Shuotao suggested FlakeCulprit since it's backed
by a try job. I think either way works, and later if we use heuristics to help
guide these try jobs (i.e. added a new test) we may want to also have
FlakeSuspectedCL as one of the heuristic results. Just an idea though.

+  """Represents information about a culprit CL for flake analysis."""
+
+  # Triage status for whether the CL is correct or not.
+  status = ndb.IntegerProperty(indexed=True, default=None)
+
+  # Url to the code review or change log associated with this change.
+  url = ndb.StringProperty(indexed=False)
+
+  # Arguments number differs from overridden method - pylint: disable=W0221
+  @classmethod
+  def Create(
+      cls, repo_name, revision, commit_position, url):  # pragma: no cover
+    instance = super(FlakeCulprit, cls).Create(
+        repo_name, revision, commit_position)
+    instance.url = url
+    return instance