On 14 June 2011 10:54, Robert Collins <robe...@robertcollins.net> 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.
After your suggestion of looking at http://bugs.python.org/issue1652 I am now running a branch through ec2 to reset the SIGPIPE handler when spawning: https://code.launchpad.net/~allenap/launchpad/rabbit-fixture-sigpipe/+merge/64531 Let's see if this works! Gavin. _______________________________________________ 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
