On Thu, Jan 28, 2016 at 10:58 PM, Bruce Dawson wrote:
>> Can you elaborate which test should be failing?
>
> Sure.
>
> The test that is failing is not in the ffmpeg repo, but it uses the ffmpeg
> repo. The Chromium test that fails (debug and release because we always
> compile ffmpeg optimized) is
> Can you elaborate which test should be failing?
Sure.
The test that is failing is not in the ffmpeg repo, but it uses the ffmpeg
repo. The Chromium test that fails (debug and release because we always
compile ffmpeg optimized) is this one:
media_unittests.exe --single-process-tests
--gtest_fil
Am 28.01.2016 22:14 schrieb "Bruce Dawson" :
>
> I hit a VS 2015 Update 1 code-gen bug that causes an string array to not
be
> null-terminated. I've already landed a patch in Chromium's downstream
copy,
> to unblock the failing test and I wanted to offer up the same patch for
the
> main ffmpeg repo
