Always write .landmines
Otherwise, if .landmines exists, and isn't clobbered by the clobber in
compile.py, every build will cause a clobber until .landmines is removed.
Trying to fix http://crbug.com/375459 brought this up. In that case
compile.py wasn't removing .landmines, which is necessary in the case
of a landmines change on two subsequent builds. If .landmines isn't
maintained, then there's nothing to diff against on the second build
and so a clobber won't be correctly triggered.
R=iannucci@chromium.org,kbr@chromium.org
BUG=376359
Review URL: https://codereview.chromium.org/293983017
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@272341 0039d316-1c4b-4281-b951-d872f2087c98
CrOS-Libchrome-Original-Commit: f3d0d1c32b222899b5fd7980d0f5b41e27354a1a
1 file changed