Update mojo sdk to rev 59145288bae55b0fce4276b017df6a1117bcf00f

Update mojo sdk to rev 59145288bae55b0fce4276b017df6a1117bcf00f

BUG=None
TBR=jamesr@chromium.org for mojo

Committed: https://crrev.com/6f6c4e614de20d2509ee53e04b1c5351db71e1c6
Cr-Commit-Position: refs/heads/master@{#308479}

[Ken Rockot(use gerrit already), 2014-12-13 00:11:20]

Patchset #1 (id:1) has been deleted

[Ken Rockot(use gerrit already), 2014-12-15 02:16:06]

Patchset #3 (id:60001) has been deleted

[Ken Rockot(use gerrit already), 2014-12-15 02:44:59]

Patchset #3 (id:80001) has been deleted

[Ken Rockot(use gerrit already), 2014-12-15 16:20:45]

rockot@chromium.org changed reviewers:
+ dalecurtis@chromium.org

[Ken Rockot(use gerrit already), 2014-12-15 16:22:05]

Dale, could you please take a look for media/mojo/services GN changes? I have
disabled the native app and media_test targets on component builds.

[DaleCurtis, 2014-12-15 18:19:06]

Are these disabled because you can't build mojo apps with the component build?

[Ken Rockot(use gerrit already), 2014-12-15 18:21:55]

On 2014/12/15 18:19:06, DaleCurtis wrote:
> Are these disabled because you can't build mojo apps with the component build?

Yep.

[DaleCurtis, 2014-12-15 18:23:58]

lgtm

[Ken Rockot(use gerrit already), 2014-12-15 18:26:09]

The CQ bit was checked by rockot@chromium.org

[commit-bot: I haz the power, 2014-12-15 18:28:17]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/799113004/100001

[jamesr, 2014-12-15 19:10:56]

jamesr@chromium.org changed reviewers:
+ jamesr@chromium.org

[jamesr, 2014-12-15 19:10:58]

lgtm

[commit-bot: I haz the power, 2014-12-15 20:48:57]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-12-15 20:49:00]

Try jobs failed on following builders:
  linux_chromium_asan_rel on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[Ken Rockot(use gerrit already), 2014-12-15 23:18:41]

rockot@chromium.org changed reviewers:
+ thestig@chromium.org

[Ken Rockot(use gerrit already), 2014-12-15 23:18:43]

Lei, could you please take a look as OWNER of tools/checklicenses?

Background in case you aren't aware is that (at least for now) we're bundling
mojo's third-party dependencies separately, despite potential overlap with
chromium's (if interested, see discussion here:
https://groups.google.com/a/chromium.org/forum/#!msg/chromium-dev/8yTrxgCk538...)

This change to checklicenses.py adds a whitelist rule for mojo's bundling of
ply.

[Lei Zhang, 2014-12-15 23:25:39]

On 2014/12/15 23:18:43, Ken Rockot wrote:
> Lei, could you please take a look as OWNER of tools/checklicenses?
> 
> Background in case you aren't aware is that (at least for now) we're bundling
> mojo's third-party dependencies separately, despite potential overlap with
> chromium's (if interested, see discussion here:
>
https://groups.google.com/a/chromium.org/forum/#!msg/chromium-dev/8yTrxgCk538...)
> 
> This change to checklicenses.py adds a whitelist rule for mojo's bundling of
> ply.

How are mojo folks dealing with when changes need to be made to third_party/ in
this case? How does one remember to update both copies? Should the
README.chromium files cross-reference each other?

[Lei Zhang, 2014-12-15 23:27:02]

lgtm

I'll just fix the third_party/ply case after you land this.

[Ken Rockot(use gerrit already), 2014-12-15 23:32:26]

On 2014/12/15 23:25:39, Lei Zhang wrote:
> On 2014/12/15 23:18:43, Ken Rockot wrote:
> > Lei, could you please take a look as OWNER of tools/checklicenses?
> > 
> > Background in case you aren't aware is that (at least for now) we're
bundling
> > mojo's third-party dependencies separately, despite potential overlap with
> > chromium's (if interested, see discussion here:
> >
>
https://groups.google.com/a/chromium.org/forum/#!msg/chromium-dev/8yTrxgCk538...)
> > 
> > This change to checklicenses.py adds a whitelist rule for mojo's bundling of
> > ply.
> 
> How are mojo folks dealing with when changes need to be made to third_party/
in
> this case? How does one remember to update both copies? Should the
> README.chromium files cross-reference each other?

They shouldn't need to be kept in sync since these dependencies are for
supporting mojo tools rather than linkable components which chromium depends on.

[Ken Rockot(use gerrit already), 2014-12-15 23:32:37]

The CQ bit was checked by rockot@chromium.org

[commit-bot: I haz the power, 2014-12-15 23:33:05]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/799113004/120001

[commit-bot: I haz the power, 2014-12-16 00:54:29]

Committed patchset #4 (id:120001)

[commit-bot: I haz the power, 2014-12-16 00:55:05]

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