mojo: Merge upstream https://github.com/domokit/mojo/commit/4bbba19b4043e57ed1bd2b9bd799729bc2342b84

mojo: Merge upstream https://github.com/domokit/mojo/commit/4bbba19b4043e57ed1bd2b9bd799729bc2342b84

Looks like mojo rolls happen only very rarely, and I don't want to wait for one.

BUG=505316
R=rockot@chromium.org

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

[Nico, 2015-08-07 22:16:32]

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

[Ken Rockot(use gerrit already), 2015-08-07 22:18:27]

lgtm

[Nico, 2015-08-07 22:18:56]

The CQ bit was checked by thakis@chromium.org

[commit-bot: I haz the power, 2015-08-07 22:19:56]

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

[commit-bot: I haz the power, 2015-08-07 23:24:32]

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

[commit-bot: I haz the power, 2015-08-07 23:24:33]

Try jobs failed on following builders:
  win_chromium_x64_rel_ng on tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)

[Nico, 2015-08-07 23:54:56]

The CQ bit was checked by thakis@chromium.org

[commit-bot: I haz the power, 2015-08-07 23:56:11]

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

[Nico, 2015-08-08 01:26:50]

Committed patchset #1 (id:1) to pending queue manually as
ac2c22e9a9d5fb219a7bb6b0ff283a88f75a17d7 (presubmit successful).

[Nico, 2015-08-24 18:46:06]

rockot, it looks like you lost this in your recent mojo roll. I'll reland it,
but is there some way to make sure that changes like this don't get lost?

[Nico, 2015-08-24 18:49:35]

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

[Ken Rockot(use gerrit already), 2015-08-24 19:02:30]

Best way is to roll more frequently so we can avoid one-off patches like
this. Even with infrequent rolls this wouldn't normally happen, but I
decided not to roll all the way up to ToT due to the complexity of doing so
after such a long period. Sorry for the trouble and thanks for re-landing!

On Mon, Aug 24, 2015 at 11:46 AM, <thakis@chromium.org> wrote:

> rockot, it looks like you lost this in your recent mojo roll. I'll reland
> it,
> but is there some way to make sure that changes like this don't get lost?
>
> https://codereview.chromium.org/1279133003/
>

To unsubscribe from this group and stop receiving emails from it, send an email
to chromium-reviews+unsubscribe@chromium.org.