|
|
DescriptionAdd specific headless_shell_win.cc and headless_content_main_delegate_win.cc
For Windows component builds
BUG=686608
Review-Url: https://codereview.chromium.org/2887033003
Cr-Original-Commit-Position: refs/heads/master@{#473494}
Committed: https://chromium.googlesource.com/chromium/src/+/5cca5ec7822a8d5594a6711b6040c90430b1772e
Review-Url: https://codereview.chromium.org/2887033003
Cr-Commit-Position: refs/heads/master@{#473517}
Committed: https://chromium.googlesource.com/chromium/src/+/722473f6b681bad4dd6dd5897d281339c81efe93
Patch Set 1 #
Total comments: 2
Patch Set 2 : Added headless_content_main_delegate_win #Patch Set 3 : Fixed weird Windows formatting #Patch Set 4 : fixed nit #Patch Set 5 : Remove virtual (was added back by mistake) #Patch Set 6 : Updated upstream #
Total comments: 1
Patch Set 7 : fix comment typo #Messages
Total messages: 47 (29 generated)
The CQ bit was checked by dvallet@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...
dvallet@chromium.org changed reviewers: + alexclarke@chromium.org, skyostil@chromium.org
WDYT? This is one way I thought of cleaning this up a bit.
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_...)
I think I prefer this, Sami WDYT? Should we go further and do this to other files too? https://codereview.chromium.org/2887033003/diff/1/headless/app/headless_shell.h File headless/app/headless_shell.h (right): https://codereview.chromium.org/2887033003/diff/1/headless/app/headless_shell... headless/app/headless_shell.h:43: virtual void DevToolsTargetReady() override; You shouldn't need both virtual and override. In fact it looks like this is breaking the compile for some platforms.
Yeah this seems like a clearer way to do things. Not sure if we could split the rest of the ifdefs out in a similar way, but this is a good start. https://codereview.chromium.org/2887033003/diff/1/headless/app/headless_shell... File headless/app/headless_shell_win.cc (right): https://codereview.chromium.org/2887033003/diff/1/headless/app/headless_shell... headless/app/headless_shell_win.cc:5: #include <memory> Do you need all these includes?
The CQ bit was checked by dvallet@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 dvallet@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 dvallet@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...
Description was changed from ========== Add specific headless_shell_win.cc file for Windows component build BUG=686608 ========== to ========== Add specific headless_shell_win.cc and headless_content_main_delegate_win.cc For Windows component builds BUG=686608 ==========
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: linux_chromium_chromeos_ozone_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 dvallet@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...
PTAL. Added also headless_content_main_delegate, although this one is not as clean.
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
lgtm
lgtm, thanks!
The CQ bit was checked by dvallet@chromium.org
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
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-simulator-xcode-clang on master.tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-simulator-xco...) mac_chromium_compile_dbg_ng on master.tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_comp...)
The CQ bit was checked by dvallet@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from skyostil@chromium.org, alexclarke@chromium.org Link to the patchset: https://codereview.chromium.org/2887033003/#ps100001 (title: "Updated upstream")
CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
CQ is committing da patch. Bot data: {"patchset_id": 100001, "attempt_start_ts": 1495413149100200, "parent_rev": "d39dae4faddc9927038ccccb4d7ec37a3fd87937", "commit_rev": "5cca5ec7822a8d5594a6711b6040c90430b1772e"}
Message was sent while issue was closed.
Description was changed from ========== Add specific headless_shell_win.cc and headless_content_main_delegate_win.cc For Windows component builds BUG=686608 ========== to ========== Add specific headless_shell_win.cc and headless_content_main_delegate_win.cc For Windows component builds BUG=686608 Review-Url: https://codereview.chromium.org/2887033003 Cr-Commit-Position: refs/heads/master@{#473494} Committed: https://chromium.googlesource.com/chromium/src/+/5cca5ec7822a8d5594a6711b6040... ==========
Message was sent while issue was closed.
Committed patchset #6 (id:100001) as https://chromium.googlesource.com/chromium/src/+/5cca5ec7822a8d5594a6711b6040...
Message was sent while issue was closed.
phistuck@gmail.com changed reviewers: + phistuck@gmail.com
Message was sent while issue was closed.
https://codereview.chromium.org/2887033003/diff/100001/headless/lib/headless_... File headless/lib/headless_content_main_delegate.cc (left): https://codereview.chromium.org/2887033003/diff/100001/headless/lib/headless_... headless/lib/headless_content_main_delegate.cc:184: // chrashpad is already enabled. s/chrashpad/crashpad
On 2017/05/22 at 06:28:39, phistuck wrote: > https://codereview.chromium.org/2887033003/diff/100001/headless/lib/headless_... > File headless/lib/headless_content_main_delegate.cc (left): > > https://codereview.chromium.org/2887033003/diff/100001/headless/lib/headless_... > headless/lib/headless_content_main_delegate.cc:184: // chrashpad is already enabled. > s/chrashpad/crashpad Thanks! Sending fix
The CQ bit was checked by dvallet@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from skyostil@chromium.org, alexclarke@chromium.org Link to the patchset: https://codereview.chromium.org/2887033003/#ps120001 (title: "fix comment typo")
CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
I am not sure it is fine to re-use a change list for multiple commits...
I've never done it, since it's a comment typo I thought of giving it a shot :) On Mon, 22 May 2017 at 16:37 <phistuck@gmail.com> wrote: > I am not sure it is fine to re-use a change list for multiple commits... > > https://codereview.chromium.org/2887033003/ > -- 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.
CQ is committing da patch. Bot data: {"patchset_id": 120001, "attempt_start_ts": 1495434886249570, "parent_rev": "7553e311e032564e696c962c1896b07cc19b226f", "commit_rev": "722473f6b681bad4dd6dd5897d281339c81efe93"}
Message was sent while issue was closed.
Description was changed from ========== Add specific headless_shell_win.cc and headless_content_main_delegate_win.cc For Windows component builds BUG=686608 Review-Url: https://codereview.chromium.org/2887033003 Cr-Commit-Position: refs/heads/master@{#473494} Committed: https://chromium.googlesource.com/chromium/src/+/5cca5ec7822a8d5594a6711b6040... ========== to ========== Add specific headless_shell_win.cc and headless_content_main_delegate_win.cc For Windows component builds BUG=686608 Review-Url: https://codereview.chromium.org/2887033003 Cr-Original-Commit-Position: refs/heads/master@{#473494} Committed: https://chromium.googlesource.com/chromium/src/+/5cca5ec7822a8d5594a6711b6040... Review-Url: https://codereview.chromium.org/2887033003 Cr-Commit-Position: refs/heads/master@{#473517} Committed: https://chromium.googlesource.com/chromium/src/+/722473f6b681bad4dd6dd5897d28... ==========
Message was sent while issue was closed.
Committed patchset #7 (id:120001) as https://chromium.googlesource.com/chromium/src/+/722473f6b681bad4dd6dd5897d28...
Message was sent while issue was closed.
FTR, patch set 6 landed as r473494 and patch set 7 landed as r473517. This CL is really confusing because it got reused to fix a typo. I was expecting to see something the size of patch set 6 when I opened this CL, but instead I saw a 1 line change. I would tell you not to do this, but we have moved on to PolyGerrit and I imagine it is more strict about not re-using CLs.
Message was sent while issue was closed.
Yup, shouldn't have done that. To be honest, I just did it to try if it was possible, hopefully gerrit doesn't allow it :) On Tue, 22 Aug 2017 at 04:30 <thestig@chromium.org> wrote: > FTR, patch set 6 landed as r473494 and patch set 7 landed as r473517. > > This CL is really confusing because it got reused to fix a typo. I was > expecting > to see something the size of patch set 6 when I opened this CL, but > instead I > saw a 1 line change. I would tell you not to do this, but we have moved on > to > PolyGerrit and I imagine it is more strict about not re-using CLs. > > https://codereview.chromium.org/2887033003/ > -- 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. |