Commit e7aa5e57 authored by Chris Sharp's avatar Chris Sharp Committed by Commit Bot

Add a chrome cleanup tool exit conditon for wrong architecture

Change-Id: I2d5955ad226d16428cc28cc8e0c908663b9346f8
Reviewed-on: https://chromium-review.googlesource.com/1237866Reviewed-by: default avatarJoe Mason <joenotcharles@chromium.org>
Commit-Queue: Chris Sharp <csharp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593727}
parent b65dfd41
...@@ -222,6 +222,11 @@ enum ResultCodeValues : ResultCode { ...@@ -222,6 +222,11 @@ enum ResultCodeValues : ResultCode {
// while the pipe was still needed by the broker process. // while the pipe was still needed by the broker process.
RESULT_CODE_ZIP_ARCHIVER_SANDBOX_DISCONNECTED_TOO_SOON = 55, RESULT_CODE_ZIP_ARCHIVER_SANDBOX_DISCONNECTED_TOO_SOON = 55,
// Used when attempting to run a 32-bit version of the tool on a 64-bit
// machine, and vice versa. Since this can result in crashes and unexpected
// result, we don't allow it.
RESULT_CODE_WRONG_ARCHITECTURE = 56,
// WHEN YOU ADD NEW EXIT CODES, DON'T FORGET TO UPDATE THE MONITORING RULES. // 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 // See http://go/chrome-cleaner-exit-codes. (Google internal only - external
// contributors please ask one of the OWNERS to do the update.) // contributors please ask one of the OWNERS to do the update.)
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment