New exit codes to signal what the engine was scanning when it timed out.

New exit codes will be used by the software reporting tool to signal
whether the engine was scanning the registry or the file system at the
moment when the watchdog terminated the process.

Change-Id: Ied95c7a8451ccbc4fb474bddddc22c2f116b8d97
Reviewed-on: https://chromium-review.googlesource.com/c/1446862Reviewed-by: Chris Sharp <csharp@chromium.org>
Commit-Queue: Chris Sharp <csharp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#627975}

components/chrome_cleaner/public/constants/result_codes.h

@@ -227,6 +227,16 @@ enum ResultCodeValues : ResultCode {
   // result, we don't allow it.
   RESULT_CODE_WRONG_ARCHITECTURE = 56,
 
+  // The process failed to complete in a reasonable amount of time and our
+  // watchdog terminated the process. At that time the engine was scanning the
+  // registry.
+  RESULT_CODE_WATCHDOG_TIMEOUT_WHILE_SCANNING_REGISTRY = 57,
+
+  // The process failed to complete in a reasonable amount of time and our
+  // watchdog terminated the process. At that time the engine was scanning the
+  // file system.
+  RESULT_CODE_WATCHDOG_TIMEOUT_WHILE_SCANNING_FILES = 58,
+
   // WHEN YOU ADD NEW EXIT CODES, DON'T FORGET TO UPDATE THE MONITORING RULES.
   // See http://go/chrome-cleaner-exit-codes. (Google internal only - external
   // contributors please ask one of the OWNERS to do the update.)