root logger in tests is very noisy

Bug #660770 reported by Robert Collins on 2010-10-14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Stuart Bishop

Bug Description

from ec2test
INFO Committing to: /tmp/testbzr-H2WFWe.tmp/devscripts.ec2test.tests.test_remote.TestResultHandling.test_doesnt_submit_to_pqm_on_failure/work/sourcecode/c/
INFO Committed revision 1.

This is a bzrlib test case, which does test isolation of everything that bzr sets up, but we're seeing these messages - I think because there is a catchall root logger in place. Either someone is failing to remove it from an earlier test, or the test environment has it installed globally - I haven't looked yet.

(sorry for edits) - there is a Logging helper around, but I still need to find it again.

description: updated
description: updated
Gary Poster (gary) on 2010-12-07
Changed in launchpad-foundations:
status: New → Triaged
importance: Undecided → Low
Stuart Bishop (stub) wrote :

For a reproducible example:

    bin/test -vv --test=distroarchseriesbinarypackage.txt --test=manage-chroot.txt

Neither of those tests emit noise when run in isolation. If distroarchseriesbinarypackage.txt is invoked before manage-test.txt though, manage-chroot.txt emits noise.

Stuart Bishop (stub) wrote :

The reset_logging function is resetting to Z3 test environment default state, undoing the customizations made in

tags: added: qa-untestable
Stuart Bishop (stub) wrote :

Much less stdout noise now. There are still a few log messages visible, but these seem to be from subprocesses not capturing their output correctly.

Changed in launchpad:
status: Triaged → Fix Released
assignee: nobody → Stuart Bishop (stub)
Curtis Hovey (sinzui) on 2011-01-11
Changed in launchpad:
milestone: none → 11.01
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers