diff options
| author | tim@chromium.org <tim@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-03-09 19:19:37 +0000 |
|---|---|---|
| committer | tim@chromium.org <tim@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-03-09 19:19:37 +0000 |
| commit | c096a9f63cf2af44f764d7de3d2cab4dcf592063 (patch) | |
| tree | ea8c296754a1bfb28de24588ec176474a1762294 /chrome/chrome_tests.gypi | |
| parent | 890c4efad2204283b8694e6b841c15375ad1390b (diff) | |
| download | chromium_src-c096a9f63cf2af44f764d7de3d2cab4dcf592063.zip chromium_src-c096a9f63cf2af44f764d7de3d2cab4dcf592063.tar.gz chromium_src-c096a9f63cf2af44f764d7de3d2cab4dcf592063.tar.bz2 | |
Make VerifyUpdatesCommand a ModelChanging variant for now as we can end
up in AttemptReuniteLostCommitResponse, change IDs, and wind up trying
to move a bookmark as a result from the wrong thread. I haven't seen
a case where it's actually _moving_, but we still call into the BookmarkModel.
It's a no-op call except for a threading assertion.
Add check to BookmarkChangeProcessor that we're on the UI thread.
BUG=37723
TEST=VerifyUpdatesCommandUnittest (added)
Review URL: http://codereview.chromium.org/689001
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@41064 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/chrome_tests.gypi')
| -rw-r--r-- | chrome/chrome_tests.gypi | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/chrome/chrome_tests.gypi b/chrome/chrome_tests.gypi index 908aeec..00ec96e 100644 --- a/chrome/chrome_tests.gypi +++ b/chrome/chrome_tests.gypi @@ -1535,6 +1535,7 @@ 'browser/sync/engine/syncer_thread_unittest.cc', 'browser/sync/engine/syncer_unittest.cc', 'browser/sync/engine/syncproto_unittest.cc', + 'browser/sync/engine/verify_updates_command_unittest.cc', 'browser/sync/glue/bookmark_data_type_controller_unittest.cc', 'browser/sync/glue/change_processor_mock.h', 'browser/sync/glue/preference_data_type_controller_unittest.cc', |