← Back to team overview

launchpad-dev team mailing list archive

Failures on Hudson

 

Hi,

	Now that I've fixed test_worker (\o/), I've turned my attention to the
errant windmill tests that are causing failures under Hudson. Since ec2
doesn't seem to want to co-operate here, I've created a new project on
Hudson -- https://hudson.wedontsleep.org/job/windmill-test/

	The branch has a little bit of extra debugging added, which shows:

test:
lp.soyuz.windmill.tests.test_archive_packages.TestArchivePackagesSourcesExtra.test_sources_extra_available
successful:
lp.soyuz.windmill.tests.test_archive_packages.TestArchivePackagesSourcesExtra.test_sources_extra_available
ERROR DISABLED: Test left new live threads: [<Thread(Thread-70, started
daemon 48011616257808)>]
Name: Thread-70
Target: <bound method WindmillHTTPServer.process_request_thread of
<windmill.server.https.WindmillHTTPServer instance at 0x11e88a28>>

test:
lp.soyuz.windmill.tests.test_archive_packages.TestArchivePackagesSourcesExtra.test_sources_extra_available
tags: zope:threads
error:
lp.soyuz.windmill.tests.test_archive_packages.TestArchivePackagesSourcesExtra.test_sources_extra_available
[ multipart
Content-Type: text/plain;charset=utf8
garbage
34
[<Thread(Thread-70, started daemon 48011616257808)>]0
]

	That to me says there's an open request that is still being dealt with,
right?

	As an added bonus for reading this far, do people find the Hudson
announces on IRC useful or annoying? (It's LPCIBot on Freenode). I'm
happy to keep it on or turn it off depending on what people say.

Thanks,
-- 
                                        Steve
Soyuz Developer
Canonical, Ltd



Follow ups