|
|
Created:
3 years, 6 months ago by chcunningham Modified:
3 years, 6 months ago CC:
chfremer+watch_chromium.org, chromium-reviews, darin-cc_chromium.org, feature-media-reviews_chromium.org, jam, mlamouri+watch-content_chromium.org, posciak+watch_chromium.org Target Ref:
refs/heads/master Project:
chromium Visibility:
Public. |
DescriptionFix MediaRemoting MediaObserver
https: //codereview.chromium.org/2905613003
Review-Url: https://codereview.chromium.org/2913153004
Cr-Commit-Position: refs/heads/master@{#477193}
Committed: https://chromium.googlesource.com/chromium/src/+/6fd962cb3e87ed2c1738f63b6a730f63badf7bf8
Patch Set 1 #Patch Set 2 : remove debugging #
Total comments: 1
Patch Set 3 : Add DCHECK #Messages
Total messages: 27 (12 generated)
The CQ bit was checked by chcunningham@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...
chcunningham@chromium.org changed reviewers: + jochen@chromium.org, miu@chromium.org
I broke MediaObserver plumbing in a previous CL, so just fixing that. Miu@, I'm surprised no tests failed?
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
can you add a test please?
On 2017/06/02 12:17:18, jochen wrote: > can you add a test please? Happy to do so. I'm not familiar with remoting details (I just found this via code review), so Yuri, please advise on the where/how for a test.
On 2017/06/02 17:32:44, chcunningham wrote: > On 2017/06/02 12:17:18, jochen wrote: > > can you add a test please? > > Happy to do so. I'm not familiar with remoting details (I just found this via > code review), so Yuri, please advise on the where/how for a test. FYI - duplicate change here https://chromium-review.googlesource.com/c/522166/
On 2017/06/02 at 12:17:18, jochen wrote: > can you add a test please? The integration tests are being worked on, tracking bug is here: https://bugs.chromium.org/p/chromium/issues/detail?id=684065 Seems like they're ready to go but wait for some refactoring to land. xjz, what's the status and what do you think of the test? Would a unit test that checks the out_media_observer is not null (ifdefed with ENABLE_MEDIA_REMOTING) be sufficient for this CL?
avayvod@chromium.org changed reviewers: + avayvod@chromium.org, xjz@chromium.org
+xjz
> Would a unit test that checks the out_media_observer is not null (ifdefed with > ENABLE_MEDIA_REMOTING) be sufficient for this CL? Works for me. Stand by for a unit test.
On 2017/06/05 17:58:19, chcunningham wrote: > > Would a unit test that checks the out_media_observer is not null (ifdefed with > > ENABLE_MEDIA_REMOTING) be sufficient for this CL? > > Works for me. Stand by for a unit test. A simple check might be good just for this CL. The browser integration tests for media remoting were hold off because the big refactoring I am currently working on. miu@: Maybe we should land some simple tests first? WDYT?
lgtm https://codereview.chromium.org/2913153004/diff/20001/content/renderer/media/... File content/renderer/media/media_factory.cc (right): https://codereview.chromium.org/2913153004/diff/20001/content/renderer/media/... content/renderer/media/media_factory.cc:352: *out_media_observer = remoting_controller->GetWeakPtr(); Hmm...Surprised the old code didn't generate a compiler error (unused var).
lgtm Just had a quick chat with miu@. The end to end browser tests will cover this regression later. For now, this type of regression will be caught in Canary. So just for this CL it's up to you whether add a test to make sure that the observer is not null when media remoting is enabled :).
Thanks all > A simple check might be good just for this CL. Done.
The CQ bit was checked by chcunningham@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from xjz@chromium.org, miu@chromium.org Link to the patchset: https://codereview.chromium.org/2913153004/#ps40001 (title: "Add DCHECK")
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: linux_android_rel_ng on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/linux_androi...)
The CQ bit was checked by chcunningham@chromium.org
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": 40001, "attempt_start_ts": 1496719326508040, "parent_rev": "14fb5d1f03c1d705a5c0e1d33904df5da7153221", "commit_rev": "6fd962cb3e87ed2c1738f63b6a730f63badf7bf8"}
Message was sent while issue was closed.
Description was changed from ========== Fix MediaRemoting MediaObserver Previous CL caused the media observer to always be null. https://codereview.chromium.org/2905613003 ========== to ========== Fix MediaRemoting MediaObserver https: //codereview.chromium.org/2905613003 Review-Url: https://codereview.chromium.org/2913153004 Cr-Commit-Position: refs/heads/master@{#477193} Committed: https://chromium.googlesource.com/chromium/src/+/6fd962cb3e87ed2c1738f63b6a73... ==========
Message was sent while issue was closed.
Committed patchset #3 (id:40001) as https://chromium.googlesource.com/chromium/src/+/6fd962cb3e87ed2c1738f63b6a73... |