Expect InitSegmentReceived() in PipelineIntegrationTest.Encrypted* tests.

Expect InitSegmentReceived() in PipelineIntegrationTest.Encrypted* tests.

This is a follow up of 37e3ddb2, which introduced the InitSegmentReceived()
call.

Since StartPipelineWithEncryptedMedia() also uses MockMediaSource, we should
also expect InitSegmentReceived() to be called. Otherwise, we'll receive
warnings about uninterested mock calls of InitSegmentReceived().

BUG=249428
TEST=This fixes expectations in existing tests.

Committed: https://crrev.com/7f437453187214d5ee1dda4c075727a342d55edc
Cr-Commit-Position: refs/heads/master@{#296099}

[xhwang, 2014-09-22 21:12:25]

xhwang@chromium.org changed reviewers:
+ wolenetz@chromium.org

[xhwang, 2014-09-22 21:12:26]

PTAL

[wolenetz, 2014-09-22 23:25:27]

lgtm (oops, I let those warnings in! Thanks for fixing!) There's a drive-by nit
that's completely orthogonal; I'm fine if it's deferred to some later CL:

https://codereview.chromium.org/588573003/diff/1/media/filters/pipeline_integ...
File media/filters/pipeline_integration_test.cc (right):

https://codereview.chromium.org/588573003/diff/1/media/filters/pipeline_integ...
media/filters/pipeline_integration_test.cc:1162: // Config changes from
encrypted to clear are not currently supported.
drive-by nit:
Is this comment still applicable? It seems it might not be, when you look at the
previous test case that is DISABLED, and also has a comment like this.

[xhwang, 2014-09-22 23:40:19]

https://codereview.chromium.org/588573003/diff/1/media/filters/pipeline_integ...
File media/filters/pipeline_integration_test.cc (right):

https://codereview.chromium.org/588573003/diff/1/media/filters/pipeline_integ...
media/filters/pipeline_integration_test.cc:1162: // Config changes from
encrypted to clear are not currently supported.
On 2014/09/22 23:25:26, wolenetz wrote:
> drive-by nit:
> Is this comment still applicable? It seems it might not be, when you look at
the
> previous test case that is DISABLED, and also has a comment like this.

This comment is still accurate. On line 1186 we expect PIPELINE_ERROR_DECODE
because of this. If you search, we have 4 places like this.

The disabled test is disabled because of other reasons: "CHECKs in
AppendAtTime()", which I don't remember what happened....

[xhwang, 2014-09-22 23:40:25]

The CQ bit was checked by xhwang@chromium.org

[commit-bot: I haz the power, 2014-09-22 23:41:35]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/588573003/1

[commit-bot: I haz the power, 2014-09-22 23:49:17]

Committed patchset #1 (id:1) as da9143fff8e2fbeace47272d571cb414150adbc4

[wolenetz, 2014-09-22 23:49:37]

https://codereview.chromium.org/588573003/diff/1/media/filters/pipeline_integ...
File media/filters/pipeline_integration_test.cc (right):

https://codereview.chromium.org/588573003/diff/1/media/filters/pipeline_integ...
media/filters/pipeline_integration_test.cc:1162: // Config changes from
encrypted to clear are not currently supported.
On 2014/09/22 23:40:19, xhwang wrote:
> On 2014/09/22 23:25:26, wolenetz wrote:
> > drive-by nit:
> > Is this comment still applicable? It seems it might not be, when you look at
> the
> > previous test case that is DISABLED, and also has a comment like this.
> 
> This comment is still accurate. On line 1186 we expect PIPELINE_ERROR_DECODE
> because of this. If you search, we have 4 places like this.
> 
> The disabled test is disabled because of other reasons: "CHECKs in
> AppendAtTime()", which I don't remember what happened....

Acknowledged.

[commit-bot: I haz the power, 2014-09-22 23:49:56]

Patchset 1 (id:??) landed as
https://crrev.com/7f437453187214d5ee1dda4c075727a342d55edc
Cr-Commit-Position: refs/heads/master@{#296099}