|
|
Chromium Code Reviews
DescriptionFix build failure with "enable_webrtc = false".
BUG=642210
TEST=
Committed: https://crrev.com/46224dddfc39d6ebaa9c3660fdd2808eb3ce861e
Cr-Commit-Position: refs/heads/master@{#415846}
Patch Set 1 #
Total comments: 2
Patch Set 2 : update mediastream files in gypi #Patch Set 3 : rebase #
Messages
Total messages: 35 (20 generated)
liushouqun@xiaomi.com changed reviewers: + esprehn@chromium.org, mcasas@chromium.org
PTAL, thanks!
https://codereview.chromium.org/2287263003/diff/1/content/content_renderer.gypi File content/content_renderer.gypi (right): https://codereview.chromium.org/2287263003/diff/1/content/content_renderer.gy... content/content_renderer.gypi:627: 'public/renderer/media_stream_audio_sink.h', Hmm I'm wondering why to single out just these few files, and not bundle all media_stream_* files under these categories -- context: WebRTC grew up to encompass not just the RTCPeerConnection-supporting classes, but also all MediaStream and derivatives work (like, e.g. the html_*_element_capturer_source). So why not move all said files in the ..._webtrc_sources categories? Also, to better understand why this is done, could you file a bug? Don't bother running master.tryserver.webrtc bots, they won't work (always fail to patch).
Description was changed from ========== Fix build failure with "enable_webrtc = false". BUG= TEST= ========== to ========== Fix build failure with "enable_webrtc = false". BUG=642210 TEST= ==========
https://codereview.chromium.org/2287263003/diff/1/content/content_renderer.gypi File content/content_renderer.gypi (right): https://codereview.chromium.org/2287263003/diff/1/content/content_renderer.gy... content/content_renderer.gypi:627: 'public/renderer/media_stream_audio_sink.h', On 2016/08/29 16:56:38, mcasas wrote: > Hmm I'm wondering why to single out just these few > files, and not bundle all media_stream_* files under > these categories -- context: WebRTC grew up to encompass > not just the RTCPeerConnection-supporting classes, > but also all MediaStream and derivatives work (like, e.g. > the html_*_element_capturer_source). > > So why not move all said files in the ..._webtrc_sources > categories? > > Also, to better understand why this is done, could you > file a bug? > > Don't bother running master.tryserver.webrtc bots, they > won't work (always fail to patch). @mcasas, I have filed a bug to tracking this issue: http://crbug.com/642210 and I'll firstly try to move MediaStream files into webrtc category.
Patchset #2 (id:20001) has been deleted
mcasas@: CL updated, moved all media stream files into webrtc_sources group.
The CQ bit was checked by mcasas@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...
On 2016/08/30 06:07:30, Shouqun1 wrote: > mcasas@: CL updated, moved all media stream files into webrtc_sources group. lgtm if bots are happy, thanks! (I just kicked a cq dry-run since that run more esoteric bots).
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
lgtm
The CQ bit was checked by liushouqun@xiaomi.com
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: chromium_presubmit on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)
The CQ bit was checked by liushouqun@xiaomi.com
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: chromium_presubmit on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)
The CQ bit was checked by shouqun@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 shouqun@chromium.org
liushouqun@xiaomi.com changed reviewers: - shouqun@chromium.org
liushouqun@xiaomi.com changed reviewers: + brettw@chromium.org
+brettw CL rebased according to https://codereview.chromium.org/2291223002, also has change in content/public, PTAL
lgtm
The CQ bit was checked by liushouqun@xiaomi.com
The patchset sent to the CQ was uploaded after l-g-t-m from esprehn@chromium.org, mcasas@chromium.org Link to the patchset: https://codereview.chromium.org/2287263003/#ps60001 (title: "rebase")
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 ========== Fix build failure with "enable_webrtc = false". BUG=642210 TEST= ========== to ========== Fix build failure with "enable_webrtc = false". BUG=642210 TEST= ==========
Message was sent while issue was closed.
Committed patchset #3 (id:60001)
Message was sent while issue was closed.
Description was changed from ========== Fix build failure with "enable_webrtc = false". BUG=642210 TEST= ========== to ========== Fix build failure with "enable_webrtc = false". BUG=642210 TEST= Committed: https://crrev.com/46224dddfc39d6ebaa9c3660fdd2808eb3ce861e Cr-Commit-Position: refs/heads/master@{#415846} ==========
Message was sent while issue was closed.
Patchset 3 (id:??) landed as https://crrev.com/46224dddfc39d6ebaa9c3660fdd2808eb3ce861e Cr-Commit-Position: refs/heads/master@{#415846} |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
