Monty Taylor 229d8f6b21 Don't treat parsing problems as async task timeout (#16458) ... * Don't treat parsing problems as async task timeout If there is a problem reading/writing the status file that manifests as not being able to parse the data, that doesn't mean the task timed out, it means there was what was likely a tempoarary problem. Move on and keep polling for success. The only things that should cause the async status to not be parseable are bugs in the async_runner. * Add comment explaining not bailing out of loop * Return different error when result is unparseable * Remove extraneous else		2016-07-06 14:26:50 -07:00
..
process	Use loop_control.loop_var directly	2016-07-01 07:03:42 +05:30
__init__.py	Making the switch to v2	2015-05-03 21:47:26 -05:00
module_common.py	Remove doubled instantiation of the zipfile (#16609)	2016-07-06 12:22:42 -07:00
play_iterator.py	Determine failed hosts with _check_failed_state() (#16566)	2016-07-05 12:26:41 +02:00
playbook_executor.py	Take previously failed/unreachable hosts into account when checking the batch	2016-06-21 16:47:38 -05:00
stats.py	Making the switch to v2	2015-05-03 21:47:26 -05:00
task_executor.py	Don't treat parsing problems as async task timeout (#16458)	2016-07-06 14:26:50 -07:00
task_queue_manager.py	Fix the way handlers are compiled and found/notified	2016-07-06 14:57:38 -05:00
task_result.py	add jimi-c's unit test for squashed skip results, tweaked is_skipped() logic to pass	2016-05-05 15:29:10 -07:00