In CR: https://chromium-review.googlesource.com/c/599013

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

commit a01abe4398443880310732b1d46d6347101489d4
Author: Matt Wolenetz <wolenetz@chromium.org>
Date: Thu Aug 03 02:58:15 2017

Fix incorrect media_pipeline_integration fuzzer seed_corpus

BUG= 751811 
R=xhwang@chromium.org,mmoroz@chromium.org
TEST=local build of this fuzzer target produces a non-trivial seed corpus zip

Change-Id: I83d7bc24428200e8581db90714e69d94393d0bcf
Reviewed-on: https://chromium-review.googlesource.com/599013
Reviewed-by: Max Moroz <mmoroz@chromium.org>
Reviewed-by: Xiaohan Wang <xhwang@chromium.org>
Commit-Queue: Matthew Wolenetz <wolenetz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#491623}
[modify] https://crrev.com/a01abe4398443880310732b1d46d6347101489d4/media/test/BUILD.gn

#3 should have fixed this, but it seems high crash rate of this fuzzer (see  bug 751011 ) that started a couple days prior is preventing my verification of clusterfuzz corpus inclusion of some more recent fragments. Hence, marking blocked and will close this once verification can be done.

 Bug 751011  should hopefully be fixed by my https://bugs.chromium.org/p/chromium/issues/detail?id=751011#c7

Update is currently pending CF confirming that issue is fixed, and also some uptick in coverage of FFmpeg FLAC-in-MP4 demux (confirming new seed corpus is ingested).

Clusterfuzz Aug 10 coverage stats and large corpus size increase demonstrate  bug 751011  is fixed and this bug is also fixed. For example, recent FLAC-in-MP4 seed corpus additions appear to be causing new "mov_read_dfla" FFmpeg demuxer coverage.