|
|
Created:
4 years, 5 months ago by Sam McNally Modified:
4 years, 3 months ago CC:
Aaron Boodman, abarth-chromium, ben+mojo_chromium.org, chrome-apps-syd-reviews_chromium.org, chromium-reviews, darin (slow to review), qsr+mojo_chromium.org, viettrungluu+watch_chromium.org, yzshen+watch_chromium.org Base URL:
https://chromium.googlesource.com/chromium/src.git@master Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionUse ChannelMojo between browser and service processes.
BUG=604282
Committed: https://crrev.com/552aab7a1adc7428456bb2016cb45b501c65a10c
Cr-Commit-Position: refs/heads/master@{#416192}
Patch Set 1 : #Patch Set 2 : #
Total comments: 4
Patch Set 3 : #Patch Set 4 : #Depends on Patchset: Messages
Total messages: 114 (103 generated)
The CQ bit was checked by sammc@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: linux_chromium_compile_dbg_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by sammc@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)
The CQ bit was checked by sammc@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...) win_clang on master.tryserver.chromium.win (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.win/builders/win_clang/builds/...)
The CQ bit was checked by sammc@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: linux_chromium_asan_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by sammc@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was checked by sammc@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: linux_chromium_chromeos_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by sammc@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was checked by sammc@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Patchset #1 (id:1) has been deleted
Patchset #2 (id:20001) has been deleted
Patchset #3 (id:40001) has been deleted
Patchset #3 (id:60001) has been deleted
Patchset #3 (id:80001) has been deleted
Patchset #3 (id:100001) has been deleted
Patchset #4 (id:120001) has been deleted
Patchset #4 (id:140001) has been deleted
Patchset #4 (id:160001) has been deleted
Patchset #5 (id:180001) has been deleted
Patchset #4 (id:200001) has been deleted
Patchset #4 (id:220001) has been deleted
Patchset #5 (id:240001) has been deleted
Patchset #5 (id:260001) has been deleted
Patchset #5 (id:280001) has been deleted
Patchset #5 (id:300001) has been deleted
Patchset #5 (id:320001) has been deleted
Patchset #5 (id:340001) has been deleted
Patchset #2 (id:120001) has been deleted
Patchset #1 (id:1) has been deleted
Patchset #2 (id:200001) has been deleted
Patchset #2 (id:220001) has been deleted
Patchset #2 (id:360001) has been deleted
Patchset #2 (id:380001) has been deleted
Patchset #2 (id:400001) has been deleted
Patchset #3 (id:420001) has been deleted
Patchset #2 (id:440001) has been deleted
Patchset #2 (id:460001) has been deleted
Patchset #1 (id:200001) has been deleted
The CQ bit was checked by sammc@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Patchset #1 (id:480001) has been deleted
Description was changed from ========== Mojo connections over named pipes for service processes. ========== to ========== Use ChannelMojo between browser and service processes. BUG=604282 ==========
Description was changed from ========== Use ChannelMojo between browser and service processes. BUG=604282 ========== to ========== Use ChannelMojo between browser and service processes. BUG=604282 ==========
The CQ bit was checked by sammc@chromium.org to run a CQ dry run
Patchset #1 (id:500001) has been deleted
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Exceeded global retry quota
The CQ bit was checked by sammc@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by sammc@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: android_arm64_dbg_recipe on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/android_arm6...)
The CQ bit was checked by sammc@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
Patchset #1 (id:520001) has been deleted
Patchset #1 (id:540001) has been deleted
The CQ bit was checked by sammc@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Patchset #1 (id:560001) has been deleted
sammc@chromium.org changed reviewers: + rockot@chromium.org, vitalybuka@chromium.org
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
LGTM with one suggestion: Can we just not use IPC::ChannelHandle and instead have a CreateChannelMessagePipe method? I have a slight preference for channel setup code explicitly referencing ChannelMojo::Create*Factory so it's more obvious what's left to convert, and if this is always wrapping a pipe handle anyway...
+Lei Zhang <thestig@chromium.org> I am OOO. And probably after that I'll remove myself from service owners. On Wed, Aug 31, 2016 at 10:11 AM <rockot@chromium.org> wrote: > LGTM with one suggestion: Can we just not use IPC::ChannelHandle and > instead > have a CreateChannelMessagePipe method? > > I have a slight preference for channel setup code explicitly referencing > ChannelMojo::Create*Factory so it's more obvious what's left to convert, > and if > this is always wrapping a pipe handle anyway... > > https://codereview.chromium.org/2139643003/ > -- 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.
The CQ bit was checked by sammc@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
sammc@chromium.org changed reviewers: + thestig@chromium.org - vitalybuka@chromium.org
On 2016/08/31 17:11:44, Ken Rockot wrote: > LGTM with one suggestion: Can we just not use IPC::ChannelHandle and instead > have a CreateChannelMessagePipe method? > > I have a slight preference for channel setup code explicitly referencing > ChannelMojo::Create*Factory so it's more obvious what's left to convert, and if > this is always wrapping a pipe handle anyway... Done.
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
lgtm https://codereview.chromium.org/2139643003/diff/590001/chrome/browser/service... File chrome/browser/service_process/service_process_control_browsertest.cc (right): https://codereview.chromium.org/2139643003/diff/590001/chrome/browser/service... chrome/browser/service_process/service_process_control_browsertest.cc:46: void LaunchServiceProcessControl(bool wait = true) { Can we avoid having default arguments? There can't be that many callers. https://codereview.chromium.org/2139643003/diff/590001/chrome/service/service... File chrome/service/service_ipc_server_unittest.cc (right): https://codereview.chromium.org/2139643003/diff/590001/chrome/service/service... chrome/service/service_ipc_server_unittest.cc:46: mojo::ScopedMessagePipeHandle channel_handle; channel_handle_ ? Fix the over variables if you'd like to.
The CQ bit was checked by sammc@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
sammc@chromium.org changed reviewers: + dcheng@chromium.org
+dcheng for chrome/common/service_messages.h https://codereview.chromium.org/2139643003/diff/590001/chrome/browser/service... File chrome/browser/service_process/service_process_control_browsertest.cc (right): https://codereview.chromium.org/2139643003/diff/590001/chrome/browser/service... chrome/browser/service_process/service_process_control_browsertest.cc:46: void LaunchServiceProcessControl(bool wait = true) { On 2016/09/01 06:12:01, Lei Zhang wrote: > Can we avoid having default arguments? There can't be that many callers. Done. https://codereview.chromium.org/2139643003/diff/590001/chrome/service/service... File chrome/service/service_ipc_server_unittest.cc (right): https://codereview.chromium.org/2139643003/diff/590001/chrome/service/service... chrome/service/service_ipc_server_unittest.cc:46: mojo::ScopedMessagePipeHandle channel_handle; On 2016/09/01 06:12:01, Lei Zhang wrote: > channel_handle_ ? Fix the over variables if you'd like to. Done.
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
The CQ bit was checked by sammc@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
Per our chat, it'd be nice to do this without the test-only IPC. This one seems fairly innocuous, but test-only IPCs are exposed in production code as well. It'd be nice to avoid adding too many of these.
On 2016/09/01 16:54:16, dcheng wrote: > Per our chat, it'd be nice to do this without the test-only IPC. This one seems > fairly innocuous, but test-only IPCs are exposed in production code as well. > It'd be nice to avoid adding too many of these. Done.
The CQ bit was checked by sammc@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from rockot@chromium.org, thestig@chromium.org Link to the patchset: https://codereview.chromium.org/2139643003/#ps630001 (title: " ")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Message was sent while issue was closed.
Description was changed from ========== Use ChannelMojo between browser and service processes. BUG=604282 ========== to ========== Use ChannelMojo between browser and service processes. BUG=604282 ==========
Message was sent while issue was closed.
Committed patchset #4 (id:630001)
Message was sent while issue was closed.
Description was changed from ========== Use ChannelMojo between browser and service processes. BUG=604282 ========== to ========== Use ChannelMojo between browser and service processes. BUG=604282 Committed: https://crrev.com/552aab7a1adc7428456bb2016cb45b501c65a10c Cr-Commit-Position: refs/heads/master@{#416192} ==========
Message was sent while issue was closed.
Patchset 4 (id:??) landed as https://crrev.com/552aab7a1adc7428456bb2016cb45b501c65a10c Cr-Commit-Position: refs/heads/master@{#416192} |