Issue 11346006: Use 1 instead of 0 for changestamp at unittest.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Issue 11346006: Use 1 instead of 0 for changestamp at unittest. (Closed)

Created:
8 years, 1 month ago by kochi

Modified:
8 years, 1 month ago

Reviewers:
kinaba

CC:
chromium-reviews, achuith+watch_chromium.org, oshima+watch_chromium.org, stevenjb+watch_chromium.org, nkostylev+watch_chromium.org, davemoore+watch_chromium.org

Base URL:
svn://svn.chromium.org/chrome/trunk/src

Visibility:
Public.

More Reviews

Description

Use 1 instead of 0 for changestamp at unittest. As 0 has some special meaning (not initialized), change to use 1 for the old changestamp. BUG=none TEST=pass unit_tests --gtest_filter="DriveFilsSystemTest.*" Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=164847