Fix pipeline integration tests for seek / duration changes.

Fix pipeline integration tests for seek / duration changes.

PipelineIntegrationTestBase now exposes GetMediaDuration(), so that
tests can seek to the start of the media, rather than assuming it to
be zero.  The ffmpeg_regression_tests would fail, previously, if the
media's start time wasn't zero, since they would seek to 0 and then
get mad that the media time was something else.

Also, this permits the pipeline to notify the client about an
indefinite duration, then notify it about a smaller one.  This
happens if the media duration isn't known initially, but then
becomes known when the end of media is found.  Previously, the
second call to Pipeline::Client::OnDurationChanged would cause
the integration test base to get mad.

Added a test case to ffmpeg_regression_tests which hits both of
these cases.

BUG=662118
TEST=ffmpeg_regression_tests

Committed: https://crrev.com/bc29809b850a2dcd2f803d4f25238085f64d7906
Cr-Commit-Position: refs/heads/master@{#429690}

[liberato (no reviews please), 2016-11-03 18:43:06]

The CQ bit was checked by liberato@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-11-03 18:43:44]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[liberato (no reviews please), 2016-11-03 18:55:56]

Description was changed from

==========
Fix pipeline integration tests for seek / duration changes.

PipelineIntegrationTestBase now exposes GetMediaDuration(), so that
tests can seek to the start of the media, rather than assuming it to
be zero.  The ffmpeg_regression_tests would fail, previously, if the
media's start time wasn't zero, since they would seek to 0 and then
get mad that the media time was something else.

Also, this permits the pipeline to notify the client about an
indefinite duration, then notify it about a smaller one.  This
happens if the media duration isn't known initially, but then
becomes known when the end of media is found.  Previously, the
second call to Pipeline::Client::OnDurationChanged would cause
the integration test base to get mad.

Added a test case to ffmpeg_regression_tests which hits both of
these cases.

BUG=662118
TEST=ffmpeg_regression_tests
==========

to

==========
Fix pipeline integration tests for seek / duration changes.

PipelineIntegrationTestBase now exposes GetMediaDuration(), so that
tests can seek to the start of the media, rather than assuming it to
be zero.  The ffmpeg_regression_tests would fail, previously, if the
media's start time wasn't zero, since they would seek to 0 and then
get mad that the media time was something else.

Also, this permits the pipeline to notify the client about an
indefinite duration, then notify it about a smaller one.  This
happens if the media duration isn't known initially, but then
becomes known when the end of media is found.  Previously, the
second call to Pipeline::Client::OnDurationChanged would cause
the integration test base to get mad.

Added a test case to ffmpeg_regression_tests which hits both of
these cases.

BUG=662118
TEST=ffmpeg_regression_tests
==========

[liberato (no reviews please), 2016-11-03 18:55:56]

liberato@chromium.org changed reviewers:
+ dalecurtis@chromium.org

[liberato (no reviews please), 2016-11-03 18:56:56]

doesn't address the actual asan failure, but fixes the test harness a bit.

will follow up with the asan repro in another CL, assuming that i get something
working.

thanks
-fl

[DaleCurtis, 2016-11-03 19:02:07]

Nice fix, lgtm!

[commit-bot: I haz the power, 2016-11-03 19:56:09]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-11-03 19:56:10]

Dry run: This issue passed the CQ dry run.

[liberato (no reviews please), 2016-11-03 20:39:11]

The CQ bit was checked by liberato@chromium.org

[commit-bot: I haz the power, 2016-11-03 20:39:52]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-11-03 20:45:33]

Description was changed from

==========
Fix pipeline integration tests for seek / duration changes.

PipelineIntegrationTestBase now exposes GetMediaDuration(), so that
tests can seek to the start of the media, rather than assuming it to
be zero.  The ffmpeg_regression_tests would fail, previously, if the
media's start time wasn't zero, since they would seek to 0 and then
get mad that the media time was something else.

Also, this permits the pipeline to notify the client about an
indefinite duration, then notify it about a smaller one.  This
happens if the media duration isn't known initially, but then
becomes known when the end of media is found.  Previously, the
second call to Pipeline::Client::OnDurationChanged would cause
the integration test base to get mad.

Added a test case to ffmpeg_regression_tests which hits both of
these cases.

BUG=662118
TEST=ffmpeg_regression_tests
==========

to

==========
Fix pipeline integration tests for seek / duration changes.

PipelineIntegrationTestBase now exposes GetMediaDuration(), so that
tests can seek to the start of the media, rather than assuming it to
be zero.  The ffmpeg_regression_tests would fail, previously, if the
media's start time wasn't zero, since they would seek to 0 and then
get mad that the media time was something else.

Also, this permits the pipeline to notify the client about an
indefinite duration, then notify it about a smaller one.  This
happens if the media duration isn't known initially, but then
becomes known when the end of media is found.  Previously, the
second call to Pipeline::Client::OnDurationChanged would cause
the integration test base to get mad.

Added a test case to ffmpeg_regression_tests which hits both of
these cases.

BUG=662118
TEST=ffmpeg_regression_tests
==========

[commit-bot: I haz the power, 2016-11-03 20:45:38]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-11-03 20:48:16]

Description was changed from

==========
Fix pipeline integration tests for seek / duration changes.

PipelineIntegrationTestBase now exposes GetMediaDuration(), so that
tests can seek to the start of the media, rather than assuming it to
be zero.  The ffmpeg_regression_tests would fail, previously, if the
media's start time wasn't zero, since they would seek to 0 and then
get mad that the media time was something else.

Also, this permits the pipeline to notify the client about an
indefinite duration, then notify it about a smaller one.  This
happens if the media duration isn't known initially, but then
becomes known when the end of media is found.  Previously, the
second call to Pipeline::Client::OnDurationChanged would cause
the integration test base to get mad.

Added a test case to ffmpeg_regression_tests which hits both of
these cases.

BUG=662118
TEST=ffmpeg_regression_tests
==========

to

==========
Fix pipeline integration tests for seek / duration changes.

PipelineIntegrationTestBase now exposes GetMediaDuration(), so that
tests can seek to the start of the media, rather than assuming it to
be zero.  The ffmpeg_regression_tests would fail, previously, if the
media's start time wasn't zero, since they would seek to 0 and then
get mad that the media time was something else.

Also, this permits the pipeline to notify the client about an
indefinite duration, then notify it about a smaller one.  This
happens if the media duration isn't known initially, but then
becomes known when the end of media is found.  Previously, the
second call to Pipeline::Client::OnDurationChanged would cause
the integration test base to get mad.

Added a test case to ffmpeg_regression_tests which hits both of
these cases.

BUG=662118
TEST=ffmpeg_regression_tests

Committed: https://crrev.com/bc29809b850a2dcd2f803d4f25238085f64d7906
Cr-Commit-Position: refs/heads/master@{#429690}
==========

[commit-bot: I haz the power, 2016-11-03 20:48:17]

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