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

..

process

Performance improvements

2016-08-08 15:58:46 -05:00

__init__.py

Making the switch to v2

2015-05-03 21:47:26 -05:00

module_common.py

(re)allow ansible_python_interpreter to contain more than 1 arg (#16247)

2016-07-26 07:46:16 -07:00

play_iterator.py

Cache tasks by uuid in PlayIterator for O(1) lookups

2016-08-10 12:49:19 -05:00

playbook_executor.py

Don't immediately return failed for any_errors_fatal tasks

2016-08-12 14:18:50 -05:00

stats.py

Making the switch to v2

2015-05-03 21:47:26 -05:00

task_executor.py

Avoid copying task parents in TaskExecutor

2016-08-08 15:58:46 -05:00

task_queue_manager.py

Don't immediately return failed for any_errors_fatal tasks

2016-08-12 14:18:50 -05:00

task_result.py

Performance improvements

2016-08-08 15:58:46 -05:00