Add a landmine to clobber broken GN bots.

Add a landmine to clobber broken GN bots.

GN bots are having trouble picking up the changes to the resouce ID
range, which was changed in https://codereview.chromium.org/734243003/.

BUG=444902
R=eroman@chromium.org, thakis@chromium.org

Committed: https://chromium.googlesource.com/chromium/src/+/d1a85aee41655ad2c016ffe22320f0b1d9571e15

[dcheng, 2014-12-23 22:45:06]

dcheng@chromium.org changed reviewers:
+ eroman@chromium.org, thakis@chromium.org

[Nico, 2014-12-23 22:48:35]

lgtm

Lame that everyone needs to clobber just because gn doesn't get this right :-(

[eroman, 2014-12-23 22:51:43]

https://codereview.chromium.org/821303002/diff/1/build/get_landmines.py
File build/get_landmines.py (right):

https://codereview.chromium.org/821303002/diff/1/build/get_landmines.py#newco...
build/get_landmines.py:66: print 'Clobber to fix GN not picking up increased ID
range (crbug.com/444902)'
Is there any way to restrict this further?
Is this a thing:

if builder() == 'gn':
  ...

If not, LGTM, thanks!

[dcheng, 2014-12-23 22:53:35]

https://codereview.chromium.org/821303002/diff/1/build/get_landmines.py
File build/get_landmines.py (right):

https://codereview.chromium.org/821303002/diff/1/build/get_landmines.py#newco...
build/get_landmines.py:66: print 'Clobber to fix GN not picking up increased ID
range (crbug.com/444902)'
On 2014/12/23 22:51:42, eroman wrote:
> Is there any way to restrict this further?
> Is this a thing:
> 
> if builder() == 'gn':
>   ...
> 
> If not, LGTM, thanks!

There doesn't seem to be atm =/

[commit-bot: I haz the power, 2014-12-23 22:55:50]

Patchset 1 (id:??) landed as
https://crrev.com/d1a85aee41655ad2c016ffe22320f0b1d9571e15
Cr-Commit-Position: refs/heads/master@{#309588}

[dcheng, 2014-12-23 22:56:01]

Committed patchset #1 (id:1) manually as
d1a85aee41655ad2c016ffe22320f0b1d9571e15 (presubmit successful).