Fix libfuzzer configurations to actually use proprietary codecs.

Fix libfuzzer configurations to actually use proprietary codecs.

These configurations were configuring proprietary codecs without
actually setting ffmpeg up for such support, so they were not
testing everything they could be.

Note: There was a duplicate config for gn_release_libfuzzer_asan,
so I just changed it to be mac only (which doesn't have a ChromeOS
codec configuration for ffmpeg).

The choice of chromeos for the linux variants allows more coverage
of codecs we ship across the breadth of linux based platforms.

BUG=571417, 638935
TEST=mb_unittest

Committed: https://crrev.com/ded04b8261c21b7a0a968c5f3cdd404c27e4131e
Cr-Commit-Position: refs/heads/master@{#413260}

[DaleCurtis, 2016-08-19 17:16:44]

dalecurtis@chromium.org changed reviewers:
+ dpranke@chromium.org, inferno@chromium.org

[inferno, 2016-08-19 18:00:43]

lgtm. thanks a lot for fixing this.

[Dirk Pranke, 2016-08-19 20:18:36]

lgtm, thanks for fixing!

https://codereview.chromium.org/2260893002/diff/1/tools/mb/mb_config.pyl
File tools/mb/mb_config.pyl (right):

https://codereview.chromium.org/2260893002/diff/1/tools/mb/mb_config.pyl#newc...
tools/mb/mb_config.pyl:2358: # chrome_with_codecs or chromeos_with_codecs
mixins.
arguably this shouldn't be a separate mixin at all, to avoid this potential
confusion (it got refactored into a separate one a while ago, but I think that
led to this mistake).

But, I wouldn't fix this at the moment, this whole file is due for some
reworking now that we can drop GYP.

[DaleCurtis, 2016-08-19 20:35:01]

The CQ bit was checked by dalecurtis@chromium.org

[commit-bot: I haz the power, 2016-08-19 20:35:46]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-08-19 22:00:49]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-08-19 22:02:08]

Description was changed from

==========
Fix libfuzzer configurations to actually use proprietary codecs.

These configurations were configuring proprietary codecs without
actually setting ffmpeg up for such support, so they were not
testing everything they could be.

Note: There was a duplicate config for gn_release_libfuzzer_asan,
so I just changed it to be mac only (which doesn't have a ChromeOS
codec configuration for ffmpeg).

The choice of chromeos for the linux variants allows more coverage
of codecs we ship across the breadth of linux based platforms.

BUG=571417, 638935
TEST=mb_unittest
==========

to

==========
Fix libfuzzer configurations to actually use proprietary codecs.

These configurations were configuring proprietary codecs without
actually setting ffmpeg up for such support, so they were not
testing everything they could be.

Note: There was a duplicate config for gn_release_libfuzzer_asan,
so I just changed it to be mac only (which doesn't have a ChromeOS
codec configuration for ffmpeg).

The choice of chromeos for the linux variants allows more coverage
of codecs we ship across the breadth of linux based platforms.

BUG=571417, 638935
TEST=mb_unittest

Committed: https://crrev.com/ded04b8261c21b7a0a968c5f3cdd404c27e4131e
Cr-Commit-Position: refs/heads/master@{#413260}
==========

[commit-bot: I haz the power, 2016-08-19 22:02:09]

Patchset 1 (id:??) landed as
https://crrev.com/ded04b8261c21b7a0a968c5f3cdd404c27e4131e
Cr-Commit-Position: refs/heads/master@{#413260}