Fix buffered range updates in media::Pipeline

media/base/pipeline_unittest.cc

Index: media/base/pipeline_unittest.cc
diff --git a/media/base/pipeline_unittest.cc b/media/base/pipeline_unittest.cc
index 6c0dfcf79f17f16ef929528898491e0cb5f43da3..5532b2039a595df8477e61c8936a8dd984e87ac7 100644
--- a/media/base/pipeline_unittest.cc
+++ b/media/base/pipeline_unittest.cc
@@ -657,7 +657,9 @@ TEST_F(PipelineTest, GetBufferedTimeRanges) {
   EXPECT_EQ(0u, pipeline_->GetBufferedTimeRanges().size());
 
   EXPECT_FALSE(pipeline_->DidLoadingProgress());
-  pipeline_->AddBufferedTimeRange(base::TimeDelta(), kDuration / 8);
+  Ranges<base::TimeDelta> ranges;
+  ranges.Add(base::TimeDelta::FromSeconds(0), kDuration / 8);

[wolenetz, 2016/01/06 19:28:41]

nit: just base::TimeDelta() is much more frequently used to represent time 0

[servolk, 2016/01/06 21:05:05]

Done.

[wolenetz, 2016/01/14 19:25:53]

Friendly nit ping (it's still FromSeconds(0) in patch set 5.)

[wolenetz, 2016/01/14 19:53:06]

Still a nit :)

+  pipeline_->OnBufferedTimeRangesChanged(ranges);
   EXPECT_TRUE(pipeline_->DidLoadingProgress());
   EXPECT_FALSE(pipeline_->DidLoadingProgress());
   EXPECT_EQ(1u, pipeline_->GetBufferedTimeRanges().size());