##// END OF EJS Templates
Don't unregister failing post-exec callbacks automatically...
Don't unregister failing post-exec callbacks automatically Instead, print a message regarding the failure, pointing to new `disable_failing_post_execute` trait for skipping failing callbacks. When this flag is False (the default), failing callbacks will continue to be called. When True, behavior is unchanged from previous, where callbacks are only allowed to fail once.

File last commit:

r1334:049617d6
r5734:f972ef86
Show More
test_combo.txt
36 lines | 923 B | text/plain | TextLexer
=======================
Combo testing example
=======================
This is a simple example that mixes ipython doctests::
In [1]: import code
In [2]: 2**12
Out[2]: 4096
with command-line example information that does *not* get executed::
$ mpirun -n 4 ipengine --controller-port=10000 --controller-ip=host0
and with literal examples of Python source code::
controller = dict(host='myhost',
engine_port=None, # default is 10105
control_port=None,
)
# keys are hostnames, values are the number of engine on that host
engines = dict(node1=2,
node2=2,
node3=2,
node3=2,
)
# Force failure to detect that this test is being run.
1/0
These source code examples are executed but no output is compared at all. An
error or failure is reported only if an exception is raised.
NOTE: the execution of pure python blocks is not yet working!