In the logtesting support module, fix the setting of logging level.

In the logtesting support module, fix the setting of logging level.

Background:

The logtesting.LoggingTestCase class sets up a logging handler with a
particular level, and attaches it to the root logger.

When messages are logged in code under tests in unit tests, the log
messages bubble up to the root logger and then are handled by this
attached handler.

Each logger and handler throws away messages below its own logging level,
and the default logging level for the root logger is logging.WARNING.
Thus the handler would accept INFO messages by default, but the handler
never sees those messages because the root logger throws them away.

This CL just changes logtesting to set the log level of the root logger
to the same level as the handler.

This CL also adds a unit test for the logtesting module.

BUG=650748
Committed: https://crrev.com/85f3c894a68932dd3f67b61d8adefeea92132bc3
Cr-Commit-Position: refs/heads/master@{#421356}

[qyearsley, 2016-09-27 18:20:18]

qyearsley@chromium.org changed reviewers:
+ jeffcarp@chromium.org

[qyearsley, 2016-09-27 18:22:12]

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

[commit-bot: I haz the power, 2016-09-27 18:22:49]

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

[qyearsley, 2016-09-27 18:30:10]

Description was changed from

==========
In the logtesting support module, fix logging level setting.

What is happening:

The logtesting.LoggingTestCase class sets up a logging handler with a
particular level, and attaches it to the root logger.

When messages are logged in code under tests in unit tests, the log
messages bubble up to the root logger and then are handled by this
attached handler.

Each logger and handler throws away messages below its own logging level,
and the default logging level for the root logger is logging.WARNING.
Thus the handler would accept INFO messages by default, but the handler
never sees those messages because the root logger throws them away.

This CL just changes logtesting to set the log level of the root logger
to the same level as the handler.

This CL also adds a unit test for the logtesting module.

BUG=650748
==========

to

==========
In the logtesting support module, fix the setting of logging level.

Background:

The logtesting.LoggingTestCase class sets up a logging handler with a
particular level, and attaches it to the root logger.

When messages are logged in code under tests in unit tests, the log
messages bubble up to the root logger and then are handled by this
attached handler.

Each logger and handler throws away messages below its own logging level,
and the default logging level for the root logger is logging.WARNING.
Thus the handler would accept INFO messages by default, but the handler
never sees those messages because the root logger throws them away.

This CL just changes logtesting to set the log level of the root logger
to the same level as the handler.

This CL also adds a unit test for the logtesting module.

BUG=650748
==========

[commit-bot: I haz the power, 2016-09-27 19:17:08]

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

[commit-bot: I haz the power, 2016-09-27 19:17:09]

Dry run: This issue passed the CQ dry run.

[jeffcarp, 2016-09-27 21:13:58]

On 2016/09/27 at 18:20:18, qyearsley wrote:
> 

lgtm

[qyearsley, 2016-09-27 22:04:00]

The CQ bit was checked by qyearsley@chromium.org

[commit-bot: I haz the power, 2016-09-27 22:04:18]

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-09-27 22:10:37]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-09-27 22:13:19]

Description was changed from

==========
In the logtesting support module, fix the setting of logging level.

Background:

The logtesting.LoggingTestCase class sets up a logging handler with a
particular level, and attaches it to the root logger.

When messages are logged in code under tests in unit tests, the log
messages bubble up to the root logger and then are handled by this
attached handler.

Each logger and handler throws away messages below its own logging level,
and the default logging level for the root logger is logging.WARNING.
Thus the handler would accept INFO messages by default, but the handler
never sees those messages because the root logger throws them away.

This CL just changes logtesting to set the log level of the root logger
to the same level as the handler.

This CL also adds a unit test for the logtesting module.

BUG=650748
==========

to

==========
In the logtesting support module, fix the setting of logging level.

Background:

The logtesting.LoggingTestCase class sets up a logging handler with a
particular level, and attaches it to the root logger.

When messages are logged in code under tests in unit tests, the log
messages bubble up to the root logger and then are handled by this
attached handler.

Each logger and handler throws away messages below its own logging level,
and the default logging level for the root logger is logging.WARNING.
Thus the handler would accept INFO messages by default, but the handler
never sees those messages because the root logger throws them away.

This CL just changes logtesting to set the log level of the root logger
to the same level as the handler.

This CL also adds a unit test for the logtesting module.

BUG=650748

Committed: https://crrev.com/85f3c894a68932dd3f67b61d8adefeea92132bc3
Cr-Commit-Position: refs/heads/master@{#421356}
==========

[commit-bot: I haz the power, 2016-09-27 22:13:19]

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