2009/8/7 John A Meinel <email address hidden>:
> So yeah, it *is* in the log, but it is hard to find. The log also
> usually has the traceback, which is often just as important. I've often
> found it a bit harder to debug than normal tests, though, because the
> information I'm looking for isn't where I expect to find it.
If they fail, I think I'd like to see:
the stderr message
the traceback
Because these error codes almost always originate in an exception
inside python it should be possible to show that directly, though it
will take a little care for tests checking for a non-zero exit.
2009/8/7 John A Meinel <email address hidden>:
> So yeah, it *is* in the log, but it is hard to find. The log also
> usually has the traceback, which is often just as important. I've often
> found it a bit harder to debug than normal tests, though, because the
> information I'm looking for isn't where I expect to find it.
If they fail, I think I'd like to see:
the stderr message
the traceback
Because these error codes almost always originate in an exception
inside python it should be possible to show that directly, though it
will take a little care for tests checking for a non-zero exit.
-- launchpad. net/~mbp/>
Martin <http://