Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(146)

Issue 1500803002: [Sync] Ensure all values of SyncProtocolErrorType are handled in ShouldRequestEarlyExit (Closed)

Created:
5 years ago by pavely
Modified:
5 years ago
Reviewers:
Nicolas Zea
CC:
chromium-reviews, tim+watch_chromium.org, zea+watch_chromium.org, maxbogue+watch_chromium.org, pvalenzuela+watch_chromium.org, plaree+watch_chromium.org, albertb+watch_chromium.org
Base URL:
https://chromium.googlesource.com/chromium/src.git@master
Target Ref:
refs/pending/heads/master
Project:
chromium
Visibility:
Public.

Description

[Sync] Ensure all values of SyncProtocolErrorType are handled in ShouldRequestEarlyExit The issue is that in ShouldRequestEarlyExit (sync_scheduler_impl.cc) switch statement doesn't explicitly handle all SyncProtocolErrorType values and therefore they are handled by default: and cause NOTREACHED(). In the current code two values that are not handled are NON_RETRIABLE_ERROR and PARTIAL_FAILURE. The change is to remove default handler from switch so that adding new error type without handling it explicitly would cause compiler error. In addition I removed NON_RETRIABLE_ERROR as it seems to be not used. BUG=565102 R=zea@chromium.org Committed: https://crrev.com/ae33a61d1c888132fdd6bf4fa9d47074d06edb87 Cr-Commit-Position: refs/heads/master@{#363283}

Patch Set 1 #

Patch Set 2 : Fix windows build #

Unified diffs Side-by-side diffs Delta from patch set Stats (+5 lines, -8 lines) Patch
M sync/engine/sync_scheduler_impl.cc View 1 2 chunks +5 lines, -3 lines 0 comments Download
M sync/protocol/sync_protocol_error.h View 1 chunk +0 lines, -4 lines 0 comments Download
M sync/protocol/sync_protocol_error.cc View 1 chunk +0 lines, -1 line 0 comments Download

Messages

Total messages: 16 (7 generated)
pavely
5 years ago (2015-12-03 22:00:46 UTC) #1
Nicolas Zea
lgtm
5 years ago (2015-12-03 22:10:05 UTC) #2
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1500803002/1 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1500803002/1
5 years ago (2015-12-03 22:25:53 UTC) #4
commit-bot: I haz the power
Try jobs failed on following builders: win8_chromium_ng on tryserver.chromium.win (JOB_TIMED_OUT, no build URL) win_chromium_compile_dbg_ng on ...
5 years ago (2015-12-04 00:08:51 UTC) #6
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1500803002/1 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1500803002/1
5 years ago (2015-12-04 00:18:57 UTC) #8
commit-bot: I haz the power
Try jobs failed on following builders: chromium_presubmit on tryserver.chromium.linux (JOB_TIMED_OUT, no build URL)
5 years ago (2015-12-04 00:39:34 UTC) #10
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1500803002/20001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1500803002/20001
5 years ago (2015-12-04 19:15:33 UTC) #13
commit-bot: I haz the power
Committed patchset #2 (id:20001)
5 years ago (2015-12-04 20:20:37 UTC) #14
commit-bot: I haz the power
5 years ago (2015-12-04 20:21:40 UTC) #16
Message was sent while issue was closed.
Patchset 2 (id:??) landed as
https://crrev.com/ae33a61d1c888132fdd6bf4fa9d47074d06edb87
Cr-Commit-Position: refs/heads/master@{#363283}

Powered by Google App Engine
This is Rietveld 408576698