[Findit] Datamodel change for triaging at CL level.

appengine/findit/model/suspected_cl_status.py

Index: appengine/findit/model/suspected_cl_status.py
diff --git a/appengine/findit/model/suspected_cl_status.py b/appengine/findit/model/suspected_cl_status.py
new file mode 100644
index 0000000000000000000000000000000000000000..a0dbc7c34b32994b99cc5e084752feb91ba107d2
--- /dev/null
+++ b/appengine/findit/model/suspected_cl_status.py
@@ -0,0 +1,18 @@
+# Copyright 2016 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.
+
+
+# Represents triage result of a suspected cl.
+CORRECT = 0
+INCORRECT = 1
+PARTIALLY_CORRECT = 2
+PARTIALLY_TRIAGED = 3
+
+
+RESULT_STATUS_TO_DESCRIPTION = {
+    CORRECT: 'Correct',
+    INCORRECT: 'Incorrect',
+    PARTIALLY_CORRECT: 'Partially Correct',

[lijeffrey, 2016/09/08 22:09:23]

so does this mean this suspected CL is correct for some builds but not for
others?

[chanli, 2016/09/08 22:32:29]

Yes.

+    PARTIALLY_TRIAGED: 'Partially triaged'

[lijeffrey, 2016/09/08 22:09:23]

does this mean the suspected CL has only been triaged for a few builds but not
all? Basically we no longer want automatic matching (if a suspected CL is marked
correct for 1 build, it still only applies to that 1 build)?

[chanli, 2016/09/08 22:32:29]

We want to compare failures before automatic triage. So we will triage builds in
group if they have the same failures.

Please refer to
https://docs.google.com/a/google.com/document/d/1xS2b7Z5RCiFBBp3R-jvTg3zfQuel...

+}