libfuzzer: add documentation recommending how to silence error logging

libfuzzer: add documentation recommending how to silence error logging

TEST=Using local md_browser.py check documentation formatting is
correct.
BUG=none

Committed: https://crrev.com/160c5986b88cd140486c9ecfb4df3e739e334b02
Cr-Commit-Position: refs/heads/master@{#415330}

[robert.bradford, 2016-08-30 15:47:50]

robert.bradford@intel.com changed reviewers:
+ inferno@chromium.org, mmoroz@chromium.org

[robert.bradford, 2016-08-30 15:47:51]

Not a technical solution to the problem but might work as an interim?

[mmoroz, 2016-08-30 15:54:01]

https://codereview.chromium.org/2290223003/diff/1/testing/libfuzzer/getting_s...
File testing/libfuzzer/getting_started.md (right):

https://codereview.chromium.org/2290223003/diff/1/testing/libfuzzer/getting_s...
testing/libfuzzer/getting_started.md:111: The best way to do that is to override
the environment used for logging in your
I think it's worth to clarify "If the target uses Chromium logging interface,
...". Because some targets (usually third party libraries) have other logging
functions and this trick won't work there.

[inferno, 2016-08-30 15:56:46]

lgtm with Max's comment addressed. We should probably mention about reducing
writing to disk as well, that can go in another cl.

[inferno, 2016-08-30 15:57:39]

Another comment.

https://codereview.chromium.org/2290223003/diff/1/testing/libfuzzer/getting_s...
File testing/libfuzzer/getting_started.md (right):

https://codereview.chromium.org/2290223003/diff/1/testing/libfuzzer/getting_s...
testing/libfuzzer/getting_started.md:107: ## Remove error message logging
s/Remove/Disable noisy

[robert.bradford, 2016-08-30 16:16:51]

mmoroz@ are you happy with this wording?

https://codereview.chromium.org/2290223003/diff/1/testing/libfuzzer/getting_s...
File testing/libfuzzer/getting_started.md (right):

https://codereview.chromium.org/2290223003/diff/1/testing/libfuzzer/getting_s...
testing/libfuzzer/getting_started.md:107: ## Remove error message logging
On 2016/08/30 15:57:39, inferno wrote:
> s/Remove/Disable noisy

Done.

https://codereview.chromium.org/2290223003/diff/1/testing/libfuzzer/getting_s...
testing/libfuzzer/getting_started.md:111: The best way to do that is to override
the environment used for logging in your
On 2016/08/30 15:54:00, mmoroz wrote:
> I think it's worth to clarify "If the target uses Chromium logging interface,
> ...". Because some targets (usually third party libraries) have other logging
> functions and this trick won't work there. 

Done.

[mmoroz, 2016-08-30 16:21:38]

LGTM, Thanks Robert!

[robert.bradford, 2016-08-30 16:22:34]

The CQ bit was checked by robert.bradford@intel.com

[robert.bradford, 2016-08-30 16:22:35]

The patchset sent to the CQ was uploaded after l-g-t-m from inferno@chromium.org
Link to the patchset: https://codereview.chromium.org/2290223003/#ps20001
(title: "adjust title; make clear this is for chromium logging")

[commit-bot: I haz the power, 2016-08-30 16:23:07]

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-30 17:04:47]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-08-30 17:06:06]

Description was changed from

==========
libfuzzer: add documentation recommending how to silence error logging

TEST=Using local md_browser.py check documentation formatting is
correct.
BUG=none
==========

to

==========
libfuzzer: add documentation recommending how to silence error logging

TEST=Using local md_browser.py check documentation formatting is
correct.
BUG=none

Committed: https://crrev.com/160c5986b88cd140486c9ecfb4df3e739e334b02
Cr-Commit-Position: refs/heads/master@{#415330}
==========

[commit-bot: I haz the power, 2016-08-30 17:06:08]

Patchset 2 (id:??) landed as
https://crrev.com/160c5986b88cd140486c9ecfb4df3e739e334b02
Cr-Commit-Position: refs/heads/master@{#415330}