Remove remaining calls to deprecated MessageLoop methods on Mac.

Remove remaining calls to deprecated MessageLoop methods on Mac.

With this CL, there is no remaining call to these methods on Mac:
- MessageLoop::PostTask
- MessageLoop::PostDelayedTask
- MessageLoop::ReleaseSoon
- MessageLoop::DeleteSoon
- MessageLoop::Run
- MessageLoop::RunUntilIdle

Note that this CL also removes calls to these methods from files that
are not built on Mac.

These calls were not migrated by the clang-tidy script used previously
for various reasons (Objective-C code, templates, macros, header files,
std::unique_ptr<MessageLoop>...).

This CL was generated manually (with the help of a few regular
expressions).

BUG=616447
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_optional_gpu_tests_rel;tryserver.chromium.mac:mac_optional_gpu_tests_rel;tryserver.chromium.win:win_optional_gpu_tests_rel
TBR=sdefresne@chromium.org (for ios/'s trivial application of this refactoring)

Committed: https://crrev.com/2df4a9ef0a0abb0c21d8994fe597c68f6637d95d
Cr-Commit-Position: refs/heads/master@{#406148}

[fdoray, 2016-07-07 14:19:03]

Description was changed from

==========
Remove remaining calls to deprecated MessageLoop methods on Mac.

Remove calls to these methods on files that compile on Mac:
- MessageLoop::PostTask
- MessageLoop::PostDelayedTask
- MessageLoop::ReleaseSoon
- MessageLoop::DeleteSoon
- MessageLoop::Run
- MessageLoop::RunUntilIdle

These calls were not migrated by the clang-tidy script used previously
for various reasons (Objective-C code, templates, macros, header files).
This CL was generated manually (with the help of a few regular
expressions).

BUG=616447
==========

to

==========
Remove remaining calls to deprecated MessageLoop methods on Mac.

Remove calls to these methods on files that compile on Mac:
- MessageLoop::PostTask
- MessageLoop::PostDelayedTask
- MessageLoop::ReleaseSoon
- MessageLoop::DeleteSoon
- MessageLoop::Run
- MessageLoop::RunUntilIdle

These calls were not migrated by the clang-tidy script used previously
for various reasons (Objective-C code, templates, macros, header files).
This CL was generated manually (with the help of a few regular
expressions).

BUG=616447
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_optional_gpu_tests_rel;tryserver.chromium.mac:mac_optional_gpu_tests_rel;tryserver.chromium.win:win_optional_gpu_tests_rel
==========

[fdoray, 2016-07-07 14:20:10]

Description was changed from

==========
Remove remaining calls to deprecated MessageLoop methods on Mac.

Remove calls to these methods on files that compile on Mac:
- MessageLoop::PostTask
- MessageLoop::PostDelayedTask
- MessageLoop::ReleaseSoon
- MessageLoop::DeleteSoon
- MessageLoop::Run
- MessageLoop::RunUntilIdle

These calls were not migrated by the clang-tidy script used previously
for various reasons (Objective-C code, templates, macros, header files).
This CL was generated manually (with the help of a few regular
expressions).

BUG=616447
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_optional_gpu_tests_rel;tryserver.chromium.mac:mac_optional_gpu_tests_rel;tryserver.chromium.win:win_optional_gpu_tests_rel
==========

to

==========
Remove remaining calls to deprecated MessageLoop methods on Mac.

Remove calls to these methods on files that compile on Mac:
- MessageLoop::PostTask
- MessageLoop::PostDelayedTask
- MessageLoop::ReleaseSoon
- MessageLoop::DeleteSoon
- MessageLoop::Run
- MessageLoop::RunUntilIdle

These calls were not migrated by the clang-tidy script used previously
for various reasons (Objective-C code, templates, macros, header files,
std::unique_ptr<MessageLoop>...).

This CL was generated manually (with the help of a few regular
expressions).

BUG=616447
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_optional_gpu_tests_rel;tryserver.chromium.mac:mac_optional_gpu_tests_rel;tryserver.chromium.win:win_optional_gpu_tests_rel
==========

[fdoray, 2016-07-08 14:11:46]

Description was changed from

==========
Remove remaining calls to deprecated MessageLoop methods on Mac.

Remove calls to these methods on files that compile on Mac:
- MessageLoop::PostTask
- MessageLoop::PostDelayedTask
- MessageLoop::ReleaseSoon
- MessageLoop::DeleteSoon
- MessageLoop::Run
- MessageLoop::RunUntilIdle

These calls were not migrated by the clang-tidy script used previously
for various reasons (Objective-C code, templates, macros, header files,
std::unique_ptr<MessageLoop>...).

This CL was generated manually (with the help of a few regular
expressions).

BUG=616447
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_optional_gpu_tests_rel;tryserver.chromium.mac:mac_optional_gpu_tests_rel;tryserver.chromium.win:win_optional_gpu_tests_rel
==========

to

==========
Remove remaining calls to deprecated MessageLoop methods on Mac.

With this CL, there is no remaining call to these methods on Mac:
- MessageLoop::PostTask
- MessageLoop::PostDelayedTask
- MessageLoop::ReleaseSoon
- MessageLoop::DeleteSoon
- MessageLoop::Run
- MessageLoop::RunUntilIdle

These calls were not migrated by the clang-tidy script used previously
for various reasons (Objective-C code, templates, macros, header files,
std::unique_ptr<MessageLoop>...).

This CL was generated manually (with the help of a few regular
expressions).

BUG=616447
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_optional_gpu_tests_rel;tryserver.chromium.mac:mac_optional_gpu_tests_rel;tryserver.chromium.win:win_optional_gpu_tests_rel
==========

[fdoray, 2016-07-08 14:15:39]

fdoray@chromium.org changed reviewers:
+ agl@chromium.org, alokp@chromium.org, bbudge@chromium.org,
caitkp@chromium.org, chcunningham@chromium.org, gab@chromium.org,
garykac@chromium.org, jam@chromium.org, jochen@chromium.org,
maxbogue@chromium.org, reillyg@chromium.org, sadrul@chromium.org,
sergeyu@chromium.org, sievers@chromium.org, thestig@chromium.org

[fdoray, 2016-07-08 14:15:40]

gab@: Can you review this CL?

Then, I'll need rubber stamp lgtms from owners: 

base/ thestig@chromium.org
chrome/ jochen@chromium.org
chromecast/ alokp@chromium.org
components/ caitkp@chromium.org
content/ jochen@chromium.org
device/ reillyg@chromium.org
extensions/ reillyg@chromium.org
gpu/ sievers@chromium.org
ios/ droger@chromium.org
jingle/ sergeyu@chromium.org
media/ chcunningham@chromium.org
net/ agl@chromium.org
ppapi/ bbudge@chromium.org
remoting/ garykac@chromium.org
services/ jam@chromium.org
sync/ maxbogue@chromium.org
third_party/WebKit/Source/web/ jochen@chromium.org
ui/ sadrul@chromium.org

Thanks!

[bbudge, 2016-07-08 14:51:26]

ppapi lgtm

[agl, 2016-07-08 15:27:52]

LGTM for net/

[fdoray, 2016-07-08 15:38:15]

fdoray@chromium.org changed reviewers:
- caitkp@chromium.org

[fdoray, 2016-07-08 15:38:16]

gab@: Can you review this CL?

Then, I'll need rubber stamp lgtms from owners: 

base/ thestig@chromium.org
chrome/ jochen@chromium.org
chromecast/ alokp@chromium.org
components/ jochen@chromium.org [previously caitkp@]
content/ jochen@chromium.org
device/ reillyg@chromium.org
extensions/ reillyg@chromium.org
gpu/ sievers@chromium.org
ios/ droger@chromium.org
jingle/ sergeyu@chromium.org
media/ chcunningham@chromium.org
net/ agl@chromium.org [done]
ppapi/ bbudge@chromium.org [done]
remoting/ garykac@chromium.org
services/ jam@chromium.org
sync/ maxbogue@chromium.org
third_party/WebKit/Source/web/ jochen@chromium.org
ui/ sadrul@chromium.org

Thanks!

[Lei Zhang, 2016-07-08 17:08:42]

https://codereview.chromium.org/2132593002/diff/50001/base/test/ios/wait_util.mm
File base/test/ios/wait_util.mm (right):

https://codereview.chromium.org/2132593002/diff/50001/base/test/ios/wait_util...
base/test/ios/wait_util.mm:31: if (message_loop) {
Can we, maybe in a follow up, replace |message_loop| with a bool? I think all
the callers pass in base::MessageLoop::current() or nullptr.

[Lei Zhang, 2016-07-08 17:10:02]

base/ and chrome/ lgtm

[alokp, 2016-07-08 17:14:58]

chromecast/ lgtm

[maxbogue, 2016-07-08 17:28:18]

sync/ lgtm

[sadrul, 2016-07-08 17:30:32]

ui/ lgtm

[Sergey Ulanov, 2016-07-08 17:31:00]

remoting and jingle LGTM

[Reilly Grant (use Gerrit), 2016-07-08 17:50:06]

lgtm

[no sievers, 2016-07-08 17:55:45]

gpu lgtm

[gab, 2016-07-08 18:36:08]

lgtm w/ comments

https://codereview.chromium.org/2132593002/diff/50001/content/renderer/render...
File content/renderer/render_thread_impl.cc (right):

https://codereview.chromium.org/2132593002/diff/50001/content/renderer/render...
content/renderer/render_thread_impl.cc:962: if (main_message_loop_)
This condition now looks a bit weird to me. Can we have a static check to match
the static action?

https://codereview.chromium.org/2132593002/diff/50001/ppapi/proxy/ppb_message...
File ppapi/proxy/ppb_message_loop_proxy.cc (right):

https://codereview.chromium.org/2132593002/diff/50001/ppapi/proxy/ppb_message...
ppapi/proxy/ppb_message_loop_proxy.cc:120: run_loop_ = previous_run_loop;
Why does |run_loop_| need to be a member if it's only accessed from this local
scope?

[chcunningham, 2016-07-08 19:39:13]

lgtm % comment

https://codereview.chromium.org/2132593002/diff/50001/media/test/pipeline_int...
File media/test/pipeline_integration_test.cc (right):

https://codereview.chromium.org/2132593002/diff/50001/media/test/pipeline_int...
media/test/pipeline_integration_test.cc:1761: message_loop_.Run();
Should this use RunLoop?

[fdoray, 2016-07-08 20:19:02]

fdoray@chromium.org changed reviewers:
+ sdefresne@chromium.org
- garykac@chromium.org

[fdoray, 2016-07-08 20:19:04]

jochen@ and jam@: Can you review this CL?

base/ thestig@chromium.org [done]
chrome/ thestig@chromium.org [done]
chromecast/ alokp@chromium.org [done]
components/ jochen@chromium.org
content/ jochen@chromium.org
device/ reillyg@chromium.org [done]
extensions/ reillyg@chromium.org [done]
gpu/ sievers@chromium.org [done]
ios/ sdefresne@chromium.org
jingle/ sergeyu@chromium.org [done]
media/ chcunningham@chromium.org [done]
net/ agl@chromium.org [done]
ppapi/ bbudge@chromium.org [done]
remoting/ sergeyu@chromium.org [done]
services/ jam@chromium.org
sync/ maxbogue@chromium.org [done]
third_party/WebKit/Source/web/ jochen@chromium.org
ui/ sadrul@chromium.org [done]

https://codereview.chromium.org/2132593002/diff/50001/content/renderer/render...
File content/renderer/render_thread_impl.cc (right):

https://codereview.chromium.org/2132593002/diff/50001/content/renderer/render...
content/renderer/render_thread_impl.cc:962: if (main_message_loop_)
On 2016/07/08 18:36:08, gab wrote:
> This condition now looks a bit weird to me. Can we have a static check to
match
> the static action?

if (main_message_loop_) isn't equivalent to checking if there is a MessageLoop
on the current thread. At least in RenderThreadImplBrowserTest, there is a
MessageLoop but main_message_loop_ is nullptr. I update the comment to make this
less weird.

https://codereview.chromium.org/2132593002/diff/50001/media/test/pipeline_int...
File media/test/pipeline_integration_test.cc (right):

https://codereview.chromium.org/2132593002/diff/50001/media/test/pipeline_int...
media/test/pipeline_integration_test.cc:1761: message_loop_.Run();
On 2016/07/08 19:39:12, chcunningham wrote:
> Should this use RunLoop?

yes, fixed in the latest patch set

[fdoray, 2016-07-08 20:21:10]

jochen@ and jam@: Can you review this CL?

base/ thestig@chromium.org [done]
chrome/ thestig@chromium.org [done]
chromecast/ alokp@chromium.org [done]
components/ jochen@chromium.org
content/ jochen@chromium.org
device/ reillyg@chromium.org [done]
extensions/ reillyg@chromium.org [done]
gpu/ sievers@chromium.org [done]
ios/ sdefresne@chromium.org
jingle/ sergeyu@chromium.org [done]
media/ chcunningham@chromium.org [done]
net/ agl@chromium.org [done]
ppapi/ bbudge@chromium.org [done]
remoting/ sergeyu@chromium.org [done]
services/ jam@chromium.org
sync/ maxbogue@chromium.org [done]
third_party/WebKit/Source/web/ jochen@chromium.org
ui/ sadrul@chromium.org [done]

https://codereview.chromium.org/2132593002/diff/50001/ppapi/proxy/ppb_message...
File ppapi/proxy/ppb_message_loop_proxy.cc (right):

https://codereview.chromium.org/2132593002/diff/50001/ppapi/proxy/ppb_message...
ppapi/proxy/ppb_message_loop_proxy.cc:120: run_loop_ = previous_run_loop;
On 2016/07/08 18:36:08, gab wrote:
> Why does |run_loop_| need to be a member if it's only accessed from this local
> scope?

I planned to use run_loop_ to quit the messageloop but I forgot. I did it in the
latest patch set.

[fdoray, 2016-07-08 20:26:11]

sdefresne@, jochen@ and jam@: Can you review this CL?

base/ thestig@chromium.org [done]
chrome/ thestig@chromium.org [done]
chromecast/ alokp@chromium.org [done]
components/ jochen@chromium.org
content/ jochen@chromium.org
device/ reillyg@chromium.org [done]
extensions/ reillyg@chromium.org [done]
gpu/ sievers@chromium.org [done]
ios/ sdefresne@chromium.org
jingle/ sergeyu@chromium.org [done]
media/ chcunningham@chromium.org [done]
net/ agl@chromium.org [done]
ppapi/ bbudge@chromium.org [done]
remoting/ sergeyu@chromium.org [done]
services/ jam@chromium.org
sync/ maxbogue@chromium.org [done]
third_party/WebKit/Source/web/ jochen@chromium.org
ui/ sadrul@chromium.org [done]

[jam, 2016-07-09 02:52:41]

lgtm

[jam, 2016-07-09 02:53:44]

On 2016/07/09 02:52:41, jam wrote:
> lgtm

btw you can TBR all these owners if you have base/ owner for the API change per
https://www.chromium.org/developers/owners-files#TOC-When-to-use-To-Be-Review...
"For widespread or refactoring changes that are mechanical or global in nature,
it is acceptable to TBR the OWNERS required for submission, as long as your
changes have had the appropriate level of review or general approval.  (For
example, if touching hundreds of files across the codebase, a thread on the
chromium-dev mailing list may be better than getting individual approval from
dozens of different OWNERS.)"

[jochen (gone - plz use gerrit), 2016-07-11 14:30:24]

lgtm

[vinodsonkusare77_gmail.com, 2016-07-11 16:05:21]

>
> https://youtu.be/s2mEASqcipA
>

-- 
You received this message because you are subscribed to the Google Groups "Blink
Reviews" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to blink-reviews+unsubscribe@chromium.org.

[vinodsonkusare77_gmail.com, 2016-07-11 16:05:21]

>
> https://youtu.be/s2mEASqcipA
>

-- 
You received this message because you are subscribed to the Google Groups
"Chromium-reviews" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to chromium-reviews+unsubscribe@chromium.org.

[gab, 2016-07-11 18:05:30]

Thanks everyone.

TBR sdefresne for ios/'s trivial application of this refactoring (I'll CQ this
on fdoray's behalf during his vacation and try to seal the deal for Mac -- IIUC
this is supposed to be the last CL on that platform).

[gab, 2016-07-11 18:06:10]

Description was changed from

==========
Remove remaining calls to deprecated MessageLoop methods on Mac.

With this CL, there is no remaining call to these methods on Mac:
- MessageLoop::PostTask
- MessageLoop::PostDelayedTask
- MessageLoop::ReleaseSoon
- MessageLoop::DeleteSoon
- MessageLoop::Run
- MessageLoop::RunUntilIdle

These calls were not migrated by the clang-tidy script used previously
for various reasons (Objective-C code, templates, macros, header files,
std::unique_ptr<MessageLoop>...).

This CL was generated manually (with the help of a few regular
expressions).

BUG=616447
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_optional_gpu_tests_rel;tryserver.chromium.mac:mac_optional_gpu_tests_rel;tryserver.chromium.win:win_optional_gpu_tests_rel
==========

to

==========
Remove remaining calls to deprecated MessageLoop methods on Mac.

With this CL, there is no remaining call to these methods on Mac:
- MessageLoop::PostTask
- MessageLoop::PostDelayedTask
- MessageLoop::ReleaseSoon
- MessageLoop::DeleteSoon
- MessageLoop::Run
- MessageLoop::RunUntilIdle

These calls were not migrated by the clang-tidy script used previously
for various reasons (Objective-C code, templates, macros, header files,
std::unique_ptr<MessageLoop>...).

This CL was generated manually (with the help of a few regular
expressions).

BUG=616447
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_optional_gpu_tests_rel;tryserver.chromium.mac:mac_optional_gpu_tests_rel;tryserver.chromium.win:win_optional_gpu_tests_rel
TBR=sdefresne@chromium.org (for ios/'s trivial application of this refactoring)
==========

[gab, 2016-07-11 18:06:10]

gab@chromium.org changed reviewers:
- vinodsonkusare77@gmail.com

[gab, 2016-07-11 18:06:19]

The CQ bit was checked by gab@chromium.org

[gab, 2016-07-11 18:06:20]

The patchset sent to the CQ was uploaded after l-g-t-m from bbudge@chromium.org,
reillyg@chromium.org, sergeyu@chromium.org, gab@chromium.org,
alokp@chromium.org, thestig@chromium.org, sievers@chromium.org,
maxbogue@chromium.org, sadrul@chromium.org, agl@chromium.org,
chcunningham@chromium.org
Link to the patchset: https://codereview.chromium.org/2132593002/#ps110001
(title: "CR gab")

[commit-bot: I haz the power, 2016-07-11 18:07:02]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-07-11 18:10:29]

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

[commit-bot: I haz the power, 2016-07-11 18:10:32]

Try jobs failed on following builders:
  ios-device on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-device/builds...)
  ios-device-gn on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-device-gn/bui...)
  ios-simulator on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-simulator/bui...)
  ios-simulator-gn on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-simulator-gn/...)
  mac_chromium_compile_dbg_ng on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_comp...)
  mac_chromium_rel_ng on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)

[sdefresne, 2016-07-12 08:58:29]

ios lgtm but maybe you want to split your CL in smaller parts

If you keep it as is, could you change description to say this applies to both
Mac and iOS?

https://codereview.chromium.org/2132593002/diff/110001/base/test/ios/wait_uti...
File base/test/ios/wait_util.mm (right):

https://codereview.chromium.org/2132593002/diff/110001/base/test/ios/wait_uti...
base/test/ios/wait_util.mm:21: MessageLoop* message_loop,
nit: can you change "message_loop" to a bool and rename it to
"run_loop_until_idle"?

[fdoray, 2016-07-18 15:18:49]

Description was changed from

==========
Remove remaining calls to deprecated MessageLoop methods on Mac.

With this CL, there is no remaining call to these methods on Mac:
- MessageLoop::PostTask
- MessageLoop::PostDelayedTask
- MessageLoop::ReleaseSoon
- MessageLoop::DeleteSoon
- MessageLoop::Run
- MessageLoop::RunUntilIdle

These calls were not migrated by the clang-tidy script used previously
for various reasons (Objective-C code, templates, macros, header files,
std::unique_ptr<MessageLoop>...).

This CL was generated manually (with the help of a few regular
expressions).

BUG=616447
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_optional_gpu_tests_rel;tryserver.chromium.mac:mac_optional_gpu_tests_rel;tryserver.chromium.win:win_optional_gpu_tests_rel
TBR=sdefresne@chromium.org (for ios/'s trivial application of this refactoring)
==========

to

==========
Remove remaining calls to deprecated MessageLoop methods on Mac.

With this CL, there is no remaining call to these methods on Mac:
- MessageLoop::PostTask
- MessageLoop::PostDelayedTask
- MessageLoop::ReleaseSoon
- MessageLoop::DeleteSoon
- MessageLoop::Run
- MessageLoop::RunUntilIdle

Note that this CL also removes calls to these methods from files that
are not built on Mac.

These calls were not migrated by the clang-tidy script used previously
for various reasons (Objective-C code, templates, macros, header files,
std::unique_ptr<MessageLoop>...).

This CL was generated manually (with the help of a few regular
expressions).

BUG=616447
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_optional_gpu_tests_rel;tryserver.chromium.mac:mac_optional_gpu_tests_rel;tryserver.chromium.win:win_optional_gpu_tests_rel
TBR=sdefresne@chromium.org (for ios/'s trivial application of this refactoring)
==========

[fdoray, 2016-07-18 20:43:29]

The CQ bit was checked by fdoray@chromium.org

[fdoray, 2016-07-18 20:43:29]

The patchset sent to the CQ was uploaded after l-g-t-m from bbudge@chromium.org,
reillyg@chromium.org, sergeyu@chromium.org, gab@chromium.org, jam@chromium.org,
sadrul@chromium.org, alokp@chromium.org, chcunningham@chromium.org,
thestig@chromium.org, sdefresne@chromium.org, maxbogue@chromium.org,
jochen@chromium.org, agl@chromium.org, sievers@chromium.org
Link to the patchset: https://codereview.chromium.org/2132593002/#ps170001
(title: "h264_vt_encoder_unittest.cc")

[fdoray, 2016-07-18 20:44:03]

https://codereview.chromium.org/2132593002/diff/110001/base/test/ios/wait_uti...
File base/test/ios/wait_util.mm (right):

https://codereview.chromium.org/2132593002/diff/110001/base/test/ios/wait_uti...
base/test/ios/wait_util.mm:21: MessageLoop* message_loop,
On 2016/07/12 08:58:29, sdefresne wrote:
> nit: can you change "message_loop" to a bool and rename it to
> "run_loop_until_idle"?

I removed changes to this file from this CL. Will refactor this in a separate
CL.

[commit-bot: I haz the power, 2016-07-18 20:44:32]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-07-18 20:44:40]

Your CL relies on deprecated CQ feature(s):
 * Specifying master names in CQ_INCLUDE_TRYBOTS part of description without
"master." prefix is deprecated:
     tryserver.chromium.linux
     tryserver.chromium.mac
     tryserver.chromium.win
   For more details, see http://crbug.com/617627.

[commit-bot: I haz the power, 2016-07-18 23:47:30]

Description was changed from

==========
Remove remaining calls to deprecated MessageLoop methods on Mac.

With this CL, there is no remaining call to these methods on Mac:
- MessageLoop::PostTask
- MessageLoop::PostDelayedTask
- MessageLoop::ReleaseSoon
- MessageLoop::DeleteSoon
- MessageLoop::Run
- MessageLoop::RunUntilIdle

Note that this CL also removes calls to these methods from files that
are not built on Mac.

These calls were not migrated by the clang-tidy script used previously
for various reasons (Objective-C code, templates, macros, header files,
std::unique_ptr<MessageLoop>...).

This CL was generated manually (with the help of a few regular
expressions).

BUG=616447
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_optional_gpu_tests_rel;tryserver.chromium.mac:mac_optional_gpu_tests_rel;tryserver.chromium.win:win_optional_gpu_tests_rel
TBR=sdefresne@chromium.org (for ios/'s trivial application of this refactoring)
==========

to

==========
Remove remaining calls to deprecated MessageLoop methods on Mac.

With this CL, there is no remaining call to these methods on Mac:
- MessageLoop::PostTask
- MessageLoop::PostDelayedTask
- MessageLoop::ReleaseSoon
- MessageLoop::DeleteSoon
- MessageLoop::Run
- MessageLoop::RunUntilIdle

Note that this CL also removes calls to these methods from files that
are not built on Mac.

These calls were not migrated by the clang-tidy script used previously
for various reasons (Objective-C code, templates, macros, header files,
std::unique_ptr<MessageLoop>...).

This CL was generated manually (with the help of a few regular
expressions).

BUG=616447
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_optional_gpu_tests_rel;tryserver.chromium.mac:mac_optional_gpu_tests_rel;tryserver.chromium.win:win_optional_gpu_tests_rel
TBR=sdefresne@chromium.org (for ios/'s trivial application of this refactoring)
==========

[commit-bot: I haz the power, 2016-07-18 23:47:33]

Committed patchset #10 (id:170001)

[commit-bot: I haz the power, 2016-07-18 23:48:11]

CQ bit was unchecked.

[commit-bot: I haz the power, 2016-07-18 23:50:08]

Description was changed from

==========
Remove remaining calls to deprecated MessageLoop methods on Mac.

With this CL, there is no remaining call to these methods on Mac:
- MessageLoop::PostTask
- MessageLoop::PostDelayedTask
- MessageLoop::ReleaseSoon
- MessageLoop::DeleteSoon
- MessageLoop::Run
- MessageLoop::RunUntilIdle

Note that this CL also removes calls to these methods from files that
are not built on Mac.

These calls were not migrated by the clang-tidy script used previously
for various reasons (Objective-C code, templates, macros, header files,
std::unique_ptr<MessageLoop>...).

This CL was generated manually (with the help of a few regular
expressions).

BUG=616447
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_optional_gpu_tests_rel;tryserver.chromium.mac:mac_optional_gpu_tests_rel;tryserver.chromium.win:win_optional_gpu_tests_rel
TBR=sdefresne@chromium.org (for ios/'s trivial application of this refactoring)
==========

to

==========
Remove remaining calls to deprecated MessageLoop methods on Mac.

With this CL, there is no remaining call to these methods on Mac:
- MessageLoop::PostTask
- MessageLoop::PostDelayedTask
- MessageLoop::ReleaseSoon
- MessageLoop::DeleteSoon
- MessageLoop::Run
- MessageLoop::RunUntilIdle

Note that this CL also removes calls to these methods from files that
are not built on Mac.

These calls were not migrated by the clang-tidy script used previously
for various reasons (Objective-C code, templates, macros, header files,
std::unique_ptr<MessageLoop>...).

This CL was generated manually (with the help of a few regular
expressions).

BUG=616447
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_optional_gpu_tests_rel;tryserver.chromium.mac:mac_optional_gpu_tests_rel;tryserver.chromium.win:win_optional_gpu_tests_rel
TBR=sdefresne@chromium.org (for ios/'s trivial application of this refactoring)

Committed: https://crrev.com/2df4a9ef0a0abb0c21d8994fe597c68f6637d95d
Cr-Commit-Position: refs/heads/master@{#406148}
==========

[commit-bot: I haz the power, 2016-07-18 23:50:11]

Patchset 10 (id:??) landed as
https://crrev.com/2df4a9ef0a0abb0c21d8994fe597c68f6637d95d
Cr-Commit-Position: refs/heads/master@{#406148}