James Cammarata c669a381d1 Don't immediately return failed for any_errors_fatal tasks ... Instead of immediately returning a failed code (indicating a break in the play execution), we internally 'or' that failure code with the result (now an integer flag instead of a boolean) so that we can properly handle the rescue/always portions of blocks and still remember that the break condition was hit. Fixes #16937		2016-08-12 14:18:50 -05:00
..
__init__.py
test_strategy_base.py	Don't immediately return failed for any_errors_fatal tasks	2016-08-12 14:18:50 -05:00