chromeos: Fix wrong error handling of SetLargestChangestamp

SetLargestChangestamp can fail when something is wrong with the disk.

BUG=None

Review URL: https://codereview.chromium.org/14189022

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@195439 0039d316-1c4b-4281-b951-d872f2087c98
parent 49df548e
......@@ -26,8 +26,8 @@ void RunOnCompleteCallback(const base::Closure& on_complete_callback,
DriveFileError error) {
DCHECK(BrowserThread::CurrentlyOn(BrowserThread::UI));
DCHECK(!on_complete_callback.is_null());
DCHECK_EQ(DRIVE_FILE_OK, error);
DLOG_IF(ERROR, error != DRIVE_FILE_OK) << "SetLargestChangeStamp failed: "
<< DriveFileErrorToString(error);
on_complete_callback.Run();
}
......
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