Temporarily make lastchange use only the git hash.

Temporarily make lastchange use only the git hash.

This will fix the currently failing browser_tests
CloudPolicyTests, which fail because the lastchange
string is too long.

TBR=scottmg@chromium.org, tandrii@chromium.org
NOTRY=True
NOTREECHECKS=True
TEST=passed browser_tests on linux_chromium_rel trybot
BUG=406783
Committed: https://crrev.com/993d8dde169387c432c706e5b7a559dcb622bcc9
Cr-Commit-Position: refs/heads/master@{#291571}

[agable, 2014-08-23 17:34:04]

On 2014/08/23 17:32:02, agable wrote:

I am TBR'ing and directly landing this CL to fix the tree.

[Ryan Tseng, 2014-08-23 18:39:32]

https://codereview.chromium.org/499063002/diff/40001/build/util/lastchange.py
File build/util/lastchange.py (right):

https://codereview.chromium.org/499063002/diff/40001/build/util/lastchange.py...
build/util/lastchange.py:113: # The following code is unreachable.
We can just delete this? Or pylint will explode (or maybe pylint isn't run here)

https://codereview.chromium.org/499063002/diff/40001/chrome/browser/chrome_br...
File chrome/browser/chrome_browser_main.cc (right):

https://codereview.chromium.org/499063002/diff/40001/chrome/browser/chrome_br...
chrome/browser/chrome_browser_main.cc:7: 
intentional change?

[tandrii(chromium), 2014-08-23 18:42:19]

LGTM, agree with Ryan's comments!

[agable, 2014-08-23 18:42:37]

https://codereview.chromium.org/499063002/diff/40001/build/util/lastchange.py
File build/util/lastchange.py (right):

https://codereview.chromium.org/499063002/diff/40001/build/util/lastchange.py...
build/util/lastchange.py:113: # The following code is unreachable.
On 2014/08/23 18:39:32, Ryan T. (EMEA time) wrote:
> We can just delete this? Or pylint will explode (or maybe pylint isn't run
here)

Yeah I suppose I can delete the code and just reland it later.

https://codereview.chromium.org/499063002/diff/40001/chrome/browser/chrome_br...
File chrome/browser/chrome_browser_main.cc (right):

https://codereview.chromium.org/499063002/diff/40001/chrome/browser/chrome_br...
chrome/browser/chrome_browser_main.cc:7: 
On 2014/08/23 18:39:32, Ryan T. (EMEA time) wrote:
> intentional change?

Yes, this was done to force the trybot to rebuild and rerun browser_tests. Now
that the affected tests have passed on the trybot on this patchset, I'm going to
reupload patchset 1 and just land that.

[agable, 2014-08-23 18:48:10]

The CQ bit was checked by agable@chromium.org

[commit-bot: I haz the power, 2014-08-23 18:49:10]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/agable@chromium.org/499063002/60001

[commit-bot: I haz the power, 2014-08-23 18:50:38]

Committed patchset #4 (60001) as b2e2e15044497d6d91601fb95528f922549dcc14

[commit-bot: I haz the power, 2014-09-10 02:30:33]

Patchset 4 (id:??) landed as
https://crrev.com/993d8dde169387c432c706e5b7a559dcb622bcc9
Cr-Commit-Position: refs/heads/master@{#291571}