[Chromecast] Make buffering logging less confusing

chromecast/media/cma/pipeline/media_pipeline_impl.cc

Index: chromecast/media/cma/pipeline/media_pipeline_impl.cc
diff --git a/chromecast/media/cma/pipeline/media_pipeline_impl.cc b/chromecast/media/cma/pipeline/media_pipeline_impl.cc
index 4000955562473c54b64a3c5b4b5a3c427b4b9f1c..14ced50a4d383c37ea7f16eac46266c695ab54b9 100644
--- a/chromecast/media/cma/pipeline/media_pipeline_impl.cc
+++ b/chromecast/media/cma/pipeline/media_pipeline_impl.cc
@@ -364,7 +364,7 @@ void MediaPipelineImpl::OnBufferingNotification(bool is_buffering) {
       // TODO(alokp): WebMediaPlayerImpl currently only handles HAVE_ENOUGH.
       // See WebMediaPlayerImpl::OnPipelineBufferingStateChanged,
       // http://crbug.com/144683.
-      LOG(WARNING) << "Ignoring buffering notification.";
+      NOTIMPLEMENTED();
     } else {
       client_.buffering_state_cb.Run(::media::BUFFERING_HAVE_ENOUGH);
     }