On 01/05/2011 06:21 PM, Avi Kivity wrote:
On 01/05/2011 06:12 PM, Avi Kivity wrote:
On 01/05/2011 05:45 PM, Michael Goldish wrote:
In complex tests (KVM) an exception string is often not informative
enough and
the traceback and source code have to be examined in order to figure
out what
In complex tests (KVM) an exception string is often not informative enough and
the traceback and source code have to be examined in order to figure out what
caused the exception. Context strings are a way for tests to provide
information about what they're doing, so that when an exception is
On Wed, Jan 05, 2011 at 05:45:26PM +0200, Michael Goldish wrote:
In complex tests (KVM) an exception string is often not informative enough and
the traceback and source code have to be examined in order to figure out what
caused the exception. Context strings are a way for tests to provide
On 01/05/2011 05:45 PM, Michael Goldish wrote:
In complex tests (KVM) an exception string is often not informative enough and
the traceback and source code have to be examined in order to figure out what
caused the exception. Context strings are a way for tests to provide
information about what
On Wed, Jan 05, 2011 at 06:12:05PM +0200, Avi Kivity wrote:
It would be nice to make the error context a stack, and to use the
with statement to manage the stack:
with error.context(main test):
foo()
with error.context(before reboot):
bar()
If foo() throws
On 01/05/2011 06:12 PM, Avi Kivity wrote:
On 01/05/2011 05:45 PM, Michael Goldish wrote:
In complex tests (KVM) an exception string is often not informative
enough and
the traceback and source code have to be examined in order to figure
out what
caused the exception. Context strings are a
On 01/05/2011 06:21 PM, Eduardo Habkost wrote:
On Wed, Jan 05, 2011 at 06:12:05PM +0200, Avi Kivity wrote:
It would be nice to make the error context a stack, and to use the
with statement to manage the stack:
with error.context(main test):
foo()
with
On Wed, Jan 05, 2011 at 06:21:35PM +0200, Avi Kivity wrote:
btw, you can have a decorator for enclosing an entire function in an
error context:
@function_error_context('migration test')
def migration_test(...):
...
@context_aware does that, but it doesn't let you set the
On 01/05/2011 06:36 PM, Eduardo Habkost wrote:
On Wed, Jan 05, 2011 at 06:21:35PM +0200, Avi Kivity wrote:
btw, you can have a decorator for enclosing an entire function in an
error context:
@function_error_context('migration test')
def migration_test(...):
...
On 01/05/2011 06:21 PM, Eduardo Habkost wrote:
On Wed, Jan 05, 2011 at 06:12:05PM +0200, Avi Kivity wrote:
It would be nice to make the error context a stack, and to use the
with statement to manage the stack:
with error.context(main test):
foo()
with error.context(before
On Wed, Jan 05, 2011 at 08:55:44PM +0200, Michael Goldish wrote:
On 01/05/2011 06:21 PM, Eduardo Habkost wrote:
By the way, I think we could make _new_context() and _pop_context() part
of the public interface (i.e. remove the _ from their names). I see
@context_aware as just a helper for a
11 matches
Mail list logo
