Errors about "No handlers found for logger" when running tox tests are problematic
Bug #1491075 reported by
Amrith Kumar
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
Fix Released
|
High
|
Amrith Kumar |
Bug Description
When I run tox (py27) the results include lines that indicate
No handlers found for logger ...
These lines are also non-deterministic because they occur in a portion of the test that runs multi-threaded.
The problem is that many of the tests (negative) cause the unit being tested to attempt to LOG an error but a logger hasn't been established.
I have a fix.
Changed in trove: | |
importance: | Undecided → High |
milestone: | none → liberty-rc1 |
Changed in trove: | |
milestone: | next → mitaka-rc1 |
status: | In Progress → Fix Released |
milestone: | mitaka-rc1 → mitaka-1 |
To post a comment you must log in.
This includes lines like
No handlers could be found for logger "trove. guestagent. backup. backupagent" guestagent. backup. backupagent" cluster. models" guestagent. strategies. storage. swift"
No handlers could be found for logger "trove.
No handlers could be found for logger "trove.
No handlers could be found for logger "trove.
and maybe others!