[issue10788] test_logging failure

Brian Quinlan added the comment: Fixed in r87673. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-b

[issue10788] test_logging failure

Vinay Sajip added the comment: I think I've found the problem: test_concurrent_futures calls logging.critical, which registers a StreamHandler. This only happens when _wait_on_event and _signal_event fail on Win32. There should be no reason to call logging.critical in a test, especially as th

[issue10788] test_logging failure

Vinay Sajip added the comment: These failures in build 363 (using r87563) would occur if some stdlib code added a handler to the root logger before the start of test_logging. I see that build 364 doesn't show this failure, and it's testing r87564. From what I can see, the only changes in r875

[issue10788] test_logging failure

New submission from Antoine Pitrou : This on the Windows Server 2008 buildbot: (http://www.python.org/dev/buildbot/all/builders/AMD64%20Windows%20Server%202008%203.x) Re-running test 'test_logging' in verbose mode test_flat (test.test_logging.BuiltinLevelsTest) ... FAIL test_nested_explicit (te