Fix no-i18n builds.

Fix no-i18n builds.

TBR=littledan@chromium.org
NOTRY=true

Committed: https://crrev.com/efc50493b71af75a62f53d120c578f79d07abcf2
Cr-Commit-Position: refs/heads/master@{#34703}

[Yang, 2016-03-11 07:24:09]

Description was changed from

==========
Fix no-i18n builds.

TBR=littledan@chromium.org
==========

to

==========
Fix no-i18n builds.

TBR=littledan@chromium.org
NOTRY=true
==========

[Yang, 2016-03-11 07:24:13]

The CQ bit was checked by yangguo@chromium.org

[commit-bot: I haz the power, 2016-03-11 07:24:23]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1783853003/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1783853003/1

[commit-bot: I haz the power, 2016-03-11 07:26:01]

Description was changed from

==========
Fix no-i18n builds.

TBR=littledan@chromium.org
NOTRY=true
==========

to

==========
Fix no-i18n builds.

TBR=littledan@chromium.org
NOTRY=true
==========

[commit-bot: I haz the power, 2016-03-11 07:26:01]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-03-11 07:26:54]

Description was changed from

==========
Fix no-i18n builds.

TBR=littledan@chromium.org
NOTRY=true
==========

to

==========
Fix no-i18n builds.

TBR=littledan@chromium.org
NOTRY=true

Committed: https://crrev.com/efc50493b71af75a62f53d120c578f79d07abcf2
Cr-Commit-Position: refs/heads/master@{#34703}
==========

[commit-bot: I haz the power, 2016-03-11 07:26:54]

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

[Dan Ehrenberg, 2016-03-11 07:29:13]

lgtm

[Dan Ehrenberg, 2016-03-11 07:30:25]

Machenbach@, would it make sense to add a noi18n build to the pre-cq to make
these issues easier to come across ahead of time?

[Michael Achenbach, 2016-03-11 07:37:40]

On 2016/03/11 07:30:25, Dan Ehrenberg wrote:
> Machenbach@, would it make sense to add a noi18n build to the pre-cq to make
> these issues easier to come across ahead of time?

Please file a bug. Principally no problem. Though, this was the first no-i18n
compile breakage that made it through in the last year I think.

[Yang, 2016-03-11 07:47:35]

On 2016/03/11 07:37:40, Michael Achenbach wrote:
> On 2016/03/11 07:30:25, Dan Ehrenberg wrote:
> > Machenbach@, would it make sense to add a noi18n build to the pre-cq to make
> > these issues easier to come across ahead of time?
> 
> Please file a bug. Principally no problem. Though, this was the first no-i18n
> compile breakage that made it through in the last year I think.

I don't think we need this just yet. Maybe if this happens one or two more
times.