diff options
author | rlarocque@chromium.org <rlarocque@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-07-31 23:00:59 +0000 |
---|---|---|
committer | rlarocque@chromium.org <rlarocque@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-07-31 23:00:59 +0000 |
commit | eb7ef82890488e0bcaabb940721fac337a2e0a93 (patch) | |
tree | 51225d9cb31f07098365e570e7471054d750e843 /sync/sync.gyp | |
parent | 674bf81ee9dc14aca23adafb65ecc1424ab85372 (diff) | |
download | chromium_src-eb7ef82890488e0bcaabb940721fac337a2e0a93.zip chromium_src-eb7ef82890488e0bcaabb940721fac337a2e0a93.tar.gz chromium_src-eb7ef82890488e0bcaabb940721fac337a2e0a93.tar.bz2 |
Fix SyncManager initialization failure crash.
This crash was introduced in r148926, which changes SyncManager init
behaviour. Previously, the SyncManager would end up with a valid
SyncScheduler regardless of whether or not the initialization failed.
This SyncScheduler would later play an important role in shutting down
the syncer. Without a scheduler, the shutdown process crashes.
The ProfileSyncServiceTest.CorruptDatabase test simulates the scenario
we fail to load a sync directory. This will result in a SyncManager
initialization failure. It is intended to test that this failure is
handled by the ProfileSyncService, SyncBackendHost and SyncManager.
BUG=139723
Review URL: https://chromiumcodereview.appspot.com/10830100
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@149306 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'sync/sync.gyp')
-rw-r--r-- | sync/sync.gyp | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/sync/sync.gyp b/sync/sync.gyp index 8ca2c19..6a38127 100644 --- a/sync/sync.gyp +++ b/sync/sync.gyp @@ -167,6 +167,8 @@ 'syncable/entry_kernel.h', 'syncable/in_memory_directory_backing_store.cc', 'syncable/in_memory_directory_backing_store.h', + 'syncable/invalid_directory_backing_store.cc', + 'syncable/invalid_directory_backing_store.h', 'syncable/metahandle_set.h', 'syncable/model_type.cc', 'syncable/mutable_entry.cc', |