Turn on LevelDB logging

Turn on LevelDB logging

This will help us diagnose corruption in the wild.

BUG=140543
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=162016

[dgrogan, 2012-10-11 23:44:33]

Josh, could you review this?

It should probably wait to land until an updated leveldb is rolled into
chromium.  As-is it seems to allow LOG files on mac and windows to be written to
/LOG when in incognito mode.

[jsbell, 2012-10-11 23:58:05]

lgtm

http://codereview.chromium.org/11098057/diff/16002/content/browser/in_process...
File content/browser/in_process_webkit/indexed_db_browsertest.cc (right):

http://codereview.chromium.org/11098057/diff/16002/content/browser/in_process...
content/browser/in_process_webkit/indexed_db_browsertest.cc:255: // Converted
pyauto tests begin here.
What is the purpose of this comment?

[dgrogan, 2012-10-12 01:41:30]

http://codereview.chromium.org/11098057/diff/16002/content/browser/in_process...
File content/browser/in_process_webkit/indexed_db_browsertest.cc (right):

http://codereview.chromium.org/11098057/diff/16002/content/browser/in_process...
content/browser/in_process_webkit/indexed_db_browsertest.cc:255: // Converted
pyauto tests begin here.
On 2012/10/11 23:58:05, jsbell wrote:
> What is the purpose of this comment?

Just makes finding the end of the "regular" browser tests easier so I know where
to put new tests.  I want to put new tests near similar tests and the pyauto
tests are different than anything else.

I obviously don't feel strongly.

[jsbell, 2012-10-12 16:41:42]

> Just makes finding the end of the "regular" browser tests easier so I know
where
> to put new tests.  I want to put new tests near similar tests and the pyauto
> tests are different than anything else.

It's just a little odd since someone reading the code starting now won't know
what pyauto refers to. Perhaps change it to "Complex multi-step tests begin
here." or something.

> I obviously don't feel strongly.

Me either. :)

[commit-bot: I haz the power, 2012-10-15 18:38:01]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/dgrogan@chromium.org/11098057/23001