Flag auto-enrollment register requests.

Flag auto-enrollment register requests.

BUG=chromium-os:23063
TEST=DeviceTokenFetcherTest.*

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=118647

[Joao da Silva, 2012-01-20 12:51:59]

Here's a smaller one :-)

[Mattias Nissler (ping if slow), 2012-01-20 12:57:11]

LGTM, but I'd rather s/is_auto_enrollment/known_machine_id/ in the entire patch
for consistency.

https://chromiumcodereview.appspot.com/9233008/diff/2001/chrome/browser/polic...
File chrome/browser/policy/device_token_fetcher.cc (right):

https://chromiumcodereview.appspot.com/9233008/diff/2001/chrome/browser/polic...
chrome/browser/policy/device_token_fetcher.cc:120:
request->set_known_machine_id(true);
Maybe call the flag known_machine_id throughout for consistency?

[Joao da Silva, 2012-01-20 14:42:35]

http://codereview.chromium.org/9233008/diff/2001/chrome/browser/policy/device...
File chrome/browser/policy/device_token_fetcher.cc (right):

http://codereview.chromium.org/9233008/diff/2001/chrome/browser/policy/device...
chrome/browser/policy/device_token_fetcher.cc:120:
request->set_known_machine_id(true);
On 2012/01/20 12:57:11, Mattias Nissler wrote:
> Maybe call the flag known_machine_id throughout for consistency?

Done.

[commit-bot: I haz the power, 2012-01-20 14:42:42]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/joaodasilva@chromium.org/9233008/10

[commit-bot: I haz the power, 2012-01-20 16:21:52]

Try job failure for 9233008-10 (retry) on mac_rel for step "browser_tests".
It's a second try, previously, step "browser_tests" failed.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=mac_rel&nu...

[commit-bot: I haz the power, 2012-01-20 16:42:26]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/joaodasilva@chromium.org/9233008/10

[commit-bot: I haz the power, 2012-01-20 18:04:44]

Try job failure for 9233008-10 (retry) on mac_rel for step "update".
It's a second try, previously, steps "browser_tests, ui_tests" failed.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=mac_rel&nu...

Step "update" is always a major failure.
Look at the try server FAQ for more details.

[commit-bot: I haz the power, 2012-01-22 11:49:26]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/joaodasilva@chromium.org/9233008/8001

[Joao da Silva, 2012-01-22 12:32:15]

@tslo, @binzhao: FYI

[commit-bot: I haz the power, 2012-01-22 14:38:40]

Try job failure for 9233008-8001 (retry) on win_rel for step "base_unittests".
It's a second try, previously, steps "base_unittests, browser_tests" failed.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win_rel&nu...