[libfuzzer] Add custom max_len parameter for boringssl fuzzers.

[libfuzzer] Add custom max_len parameter for boringssl fuzzers.

R=aizatsky@chromium.org, davidben@chromium.org, ochang@chromium.org
BUG=569578
Committed: https://crrev.com/146a2e8e36a2d1bd2bcd5999b14f4cd8ba80c499
Cr-Commit-Position: refs/heads/master@{#390340}

[davidben, 2016-04-12 14:57:16]

lgtm

[aizatsky, 2016-04-12 17:47:54]

lgtm

[mmoroz, 2016-04-13 08:23:43]

The CQ bit was checked by mmoroz@chromium.org

[commit-bot: I haz the power, 2016-04-13 08:23:56]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1885493002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1885493002/1

[commit-bot: I haz the power, 2016-04-13 08:55:51]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-04-13 08:55:52]

Try jobs failed on following builders:
  linux_chromium_clobber_rel_ng on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[mmoroz, 2016-04-13 09:59:55]

The CQ bit was checked by mmoroz@chromium.org

[commit-bot: I haz the power, 2016-04-13 10:00:10]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1885493002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1885493002/1

[commit-bot: I haz the power, 2016-04-13 10:21:04]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-04-13 10:21:04]

Try jobs failed on following builders:
  linux_chromium_clobber_rel_ng on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[mmoroz, 2016-04-13 10:44:20]

On 2016/04/13 10:21:04, commit-bot: I haz the power wrote:
> Try jobs failed on following builders:
>   linux_chromium_clobber_rel_ng on tryserver.chromium.linux (JOB_FAILED,
>
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

Looks like broken goma prevents us from building:

Traceback (most recent call last):
  File "/b/build/scripts/slave/compile.py", line 1338, in <module>
error: failed to start goma; fallback has been disabled
    sys.exit(real_main())
  File "/b/build/scripts/slave/compile.py", line 1334, in real_main
    return main(options, args)
  File "/b/build/scripts/slave/compile.py", line 857, in main_ninja
    goma_ready = goma_setup(options, env)
  File "/b/build/scripts/slave/compile.py", line 213, in goma_setup
    raise Exception('failed to start goma')
Exception: failed to start goma
step returned non-zero exit code: 1

[mmoroz, 2016-04-14 09:38:24]

The CQ bit was checked by mmoroz@chromium.org

[commit-bot: I haz the power, 2016-04-14 09:38:34]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1885493002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1885493002/1

[commit-bot: I haz the power, 2016-04-14 10:11:32]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-04-14 10:11:33]

Try jobs failed on following builders:
  linux_chromium_clobber_rel_ng on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[pgervais, 2016-04-14 22:22:26]

The CQ bit was checked by pgervais@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-04-14 22:22:51]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1885493002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1885493002/1

[commit-bot: I haz the power, 2016-04-14 22:42:11]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-04-14 22:42:12]

Dry run: Try jobs failed on following builders:
  linux_chromium_clobber_rel_ng on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[mmoroz, 2016-04-15 10:21:29]

The CQ bit was checked by mmoroz@chromium.org

[commit-bot: I haz the power, 2016-04-15 10:21:42]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1885493002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1885493002/1

[commit-bot: I haz the power, 2016-04-15 11:02:01]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-04-15 11:02:02]

Try jobs failed on following builders:
  linux_chromium_clobber_rel_ng on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[pgervais, 2016-04-18 17:07:12]

Description was changed from

==========
[libfuzzer] Add custom max_len parameter for boringssl fuzzers.

R=aizatsky@chromium.org, davidben@chromium.org, ochang@chromium.org
BUG=569578
==========

to

==========
[libfuzzer] Add custom max_len parameter for boringssl fuzzers.

R=aizatsky@chromium.org, davidben@chromium.org, ochang@chromium.org
BUG=569578
==========

[pgervais, 2016-04-18 17:07:12]

pgervais@chromium.org changed reviewers:
- pgervais@chromium.org

[mmoroz, 2016-04-26 17:15:13]

The CQ bit was checked by mmoroz@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-04-26 17:15:33]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1885493002/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1885493002/20001

[commit-bot: I haz the power, 2016-04-26 17:46:29]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-04-26 17:46:30]

Dry run: Try jobs failed on following builders:
  linux_chromium_clobber_rel_ng on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[mmoroz, 2016-04-27 11:30:23]

The CQ bit was checked by mmoroz@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-04-27 11:30:42]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1885493002/40001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1885493002/40001

[commit-bot: I haz the power, 2016-04-27 12:24:08]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-04-27 12:24:10]

Dry run: This issue passed the CQ dry run.

[mmoroz, 2016-04-27 14:09:36]

On 2016/04/27 12:24:10, commit-bot: I haz the power wrote:
> Dry run: This issue passed the CQ dry run.

Not bad :)
Mike, are you sure that we need that depfile?

If yes, which another workaround may we use?

[aizatsky, 2016-04-27 18:01:10]

On 2016/04/27 14:09:36, mmoroz wrote:
> On 2016/04/27 12:24:10, commit-bot: I haz the power wrote:
> > Dry run: This issue passed the CQ dry run.
> 
> Not bad :)
> Mike, are you sure that we need that depfile?
> 
> If yes, which another workaround may we use?

let's live without it.

[davidben, 2016-04-27 18:06:22]

lgtm

https://codereview.chromium.org/1885493002/diff/40001/third_party/boringssl/B...
File third_party/boringssl/BUILD.gn (right):

https://codereview.chromium.org/1885493002/diff/40001/third_party/boringssl/B...
third_party/boringssl/BUILD.gn:189: libfuzzer_options = [ "max_len=4096" ]
Oof. Sorry, I completely forgot this was in the pipeline when I made this a
foreach. In a follow-up, I'll see about making these definitions live in the
BoringSSL repository somewhere.

[mmoroz, 2016-04-28 10:27:21]

Thanks! Let's proceed with this for now.

[mmoroz, 2016-04-28 10:27:31]

The CQ bit was checked by mmoroz@chromium.org

[mmoroz, 2016-04-28 10:27:32]

The patchset sent to the CQ was uploaded after l-g-t-m from
aizatsky@chromium.org
Link to the patchset: https://codereview.chromium.org/1885493002/#ps40001
(title: "Remove depfile for dry run to test a possible fix.")

[commit-bot: I haz the power, 2016-04-28 10:27:44]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1885493002/40001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1885493002/40001

[commit-bot: I haz the power, 2016-04-28 10:32:47]

Description was changed from

==========
[libfuzzer] Add custom max_len parameter for boringssl fuzzers.

R=aizatsky@chromium.org, davidben@chromium.org, ochang@chromium.org
BUG=569578
==========

to

==========
[libfuzzer] Add custom max_len parameter for boringssl fuzzers.

R=aizatsky@chromium.org, davidben@chromium.org, ochang@chromium.org
BUG=569578
==========

[commit-bot: I haz the power, 2016-04-28 10:32:48]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2016-04-30 17:17:20]

Patchset 3 (id:??) landed as
https://crrev.com/146a2e8e36a2d1bd2bcd5999b14f4cd8ba80c499
Cr-Commit-Position: refs/heads/master@{#390340}

[commit-bot: I haz the power, 2016-04-30 17:55:02]

Description was changed from

==========
[libfuzzer] Add custom max_len parameter for boringssl fuzzers.

R=aizatsky@chromium.org, davidben@chromium.org, ochang@chromium.org
BUG=569578
==========

to

==========
[libfuzzer] Add custom max_len parameter for boringssl fuzzers.

R=aizatsky@chromium.org, davidben@chromium.org, ochang@chromium.org
BUG=569578

Committed: https://crrev.com/146a2e8e36a2d1bd2bcd5999b14f4cd8ba80c499
Cr-Commit-Position: refs/heads/master@{#390340}
==========