tests leave threads behind
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
loggerhead |
Triaged
|
Low
|
Unassigned | ||
loggerhead-breezy |
Triaged
|
Low
|
Unassigned |
Bug Description
As part of getting the test suite to run under Launchpad, I see these new warnings:
The following test left new threads behind:
test_run_script (loggerhead.
New thread(s): [<Thread(Thread-16, started daemon 140427624232704)>, <Thread(Thread-18, started daemon 140427632625408)>, <Thread(Thread-17, started daemon 140427615840000)>, <Thread(Thread-14, started daemon 140427693524736)>]
test_files_file (loggerhead.
test_view_folder (loggerhead.
test_changes (loggerhead.
test_inventory (loggerhead.
test_get (loggerhead.
test_head (loggerhead.
test_no_access (loggerhead.
test_annotate (loggerhead.
test_changes (loggerhead.
test_changes_
test_changes_
test_changes_
test_inventory (loggerhead.
test_inventory
test_inventory
test_revision (loggerhead.
test_author_
test_authors_
test_html_escape (loggerhead.
test_html_format (loggerhead.
launchpad_
launchpad_
launchpad_
launchpad_
launchpad_
Ran 79 tests with 0 failures and 0 errors in 3.757 seconds.
Tear down zope.testing.
Total: 81 tests, 0 failures, 0 errors in 14.607 seconds.
I have a feeling something in the 'setUpLoggerhead' sort of functions is spawning a new thread, and not joining it correctly.
It doesn't seem to cause the test suite to fail, so it doesn't block us from running the tests as part of the loggerhead suite.
Note that bzr's test runner doesn't seem to complain about threads leaking, so it might be specific to Launchpad's test runner. (though that seems odd.)
Changed in loggerhead-breezy: | |
status: | New → Triaged |
importance: | Undecided → Low |
launchpads test runner does indeed have a thread introspection thing. whether that is a good idea is a separate discussion :)