[py-dev] unclean shutdown of py.test

[holger krekel]

Hi Gordon,

On Mon, Nov 09, 2009 at 10:48 +1100, Gordon Wrigley wrote:
> Actually it would probably be more accurate to say that all output is
> captured. And so I don't see any of my output, both when the test
> fails and when I run with -s.

Ah, do you mean that --boxed and a crashing process does not
give you the output?  

Currently only a completed test will convey back capturing information 
but i can see that particularly in the crashing case it's
interesting to see the output - could you file an issue for that? 

cheers,
holger

> 
> On Mon, Nov 9, 2009 at 9:45 AM, Gordon Wrigley <py-dev at tolomea.com> wrote:
> >> If you have os.fork ... what happens if you run with the "--boxed" option?
> >
> > While py.test seems to come down somewhat cleanly I get no output
> > capturing at all, even with -s? is this expected behavior?
> > I forgot to mention this in the original email but the main reason I
> > want py.test to come down cleanly is so I can get at the captured
> > output.
> >
> > G
> >
> 

--