The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/bc29809b850a2dcd2f803d4f25238085f64d7906

commit bc29809b850a2dcd2f803d4f25238085f64d7906
Author: liberato <liberato@chromium.org>
Date: Thu Nov 03 20:45:08 2016

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

Review-Url: https://codereview.chromium.org/2479633002
Cr-Commit-Position: refs/heads/master@{#429690}

[modify] https://crrev.com/bc29809b850a2dcd2f803d4f25238085f64d7906/media/ffmpeg/ffmpeg_regression_tests.cc
[modify] https://crrev.com/bc29809b850a2dcd2f803d4f25238085f64d7906/media/test/pipeline_integration_test_base.cc
[modify] https://crrev.com/bc29809b850a2dcd2f803d4f25238085f64d7906/media/test/pipeline_integration_test_base.h