On Jun 14, 2011, at 09:54 PM, Robert Collins wrote: >We got our original test fixture code from U1 which runs up ephemeral >servers as part of their test suite. Unlike use they start that from >outside the test suite. So one possibility is that its the old 'python >tramps all over SIGPIPE' behaviour tripping us up. We run rabbit from >within python so that each worker in parallel test mode can get its >own rabbit and not stomp on other tests.
If this is indeed the problem, it shouldn't be too difficult to work around. During my last stint as Ubuntu patch pilot, I reviewed this change to ubuntu-dev-tools that does just that: https://code.launchpad.net/~broder/ubuntu-dev-tools/fix-785854/+merge/62180 The reasons I marked this as Needs Fixing wouldn't be relevant for a Launchpad-specific workaround that does the same thing. Also note that the fix for the upstream bug: http://bugs.python.org/issue1652 didn't make it into Python 2.7 unfortunately, but did make it into Python 3.2. Not that that helps Launchpad much. ;) Just saying that Python 2's SIGPIPE unfriendliness shouldn't be that much of an impediment in practice. -Barry
signature.asc
Description: PGP signature
_______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : launchpad-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
