ec2test attached corrupted subunit stream

[Robert Collins]

when my lognamer branch revno 11061 was run on ec2test, the attached logfile was generated; it has been damaged - probably by mixing stderr and stdout indiscriminately, or alternatively by \r\n mangling.

[Jonathan Lange (jml)]

Can you please explain how it's corrupted? It looks perfectly fine to me.

[Robert Collins (lifeless)]

Run it through subunit.

[Jonathan Lange (jml)]

I had a look at this. The root cause is mixing stdout & stderr. It's easy to change ec2test/remote.py to discard stderr, it's quite hard to change it to include stderr in the merged format that it's in now as well as keep a "pure" stdout for subunit parsing purposes.

For me, the easiest way to fix this bug properly would be to switch remote.py to use Twisted. This would make bug 419694 easier to fix too.