manual backport of win_async test changes from devel
This commit is contained in:
parent
c2f9846278
commit
d637559825
2 changed files with 27 additions and 26 deletions
|
@ -138,31 +138,32 @@
|
||||||
- asyncresult | failed == true
|
- asyncresult | failed == true
|
||||||
- asyncresult.msg is search('failing via exception')
|
- asyncresult.msg is search('failing via exception')
|
||||||
|
|
||||||
- name: loop async success
|
# FUTURE: figure out why the last iteration of this test often fails on shippable
|
||||||
async_test:
|
#- name: loop async success
|
||||||
sleep_delay_sec: 3
|
# async_test:
|
||||||
async: 10
|
# sleep_delay_sec: 3
|
||||||
poll: 0
|
# async: 10
|
||||||
with_sequence: start=1 end=4
|
# poll: 0
|
||||||
register: async_many
|
# with_sequence: start=1 end=4
|
||||||
|
# register: async_many
|
||||||
- name: wait for completion
|
#
|
||||||
async_status:
|
#- name: wait for completion
|
||||||
jid: "{{ item }}"
|
# async_status:
|
||||||
register: asyncout
|
# jid: "{{ item }}"
|
||||||
until: asyncout.finished == 1
|
# register: asyncout
|
||||||
retries: 10
|
# until: asyncout.finished == 1
|
||||||
delay: 1
|
# retries: 10
|
||||||
with_items: "{{ async_many.results | map(attribute='ansible_job_id') | list }}"
|
# delay: 1
|
||||||
|
# with_items: "{{ async_many.results | map(attribute='ansible_job_id') | list }}"
|
||||||
- name: validate results
|
#
|
||||||
assert:
|
#- name: validate results
|
||||||
that:
|
# assert:
|
||||||
- item.finished == 1
|
# that:
|
||||||
- item.slept_sec == 3
|
# - item.finished == 1
|
||||||
- item.changed == true
|
# - item.slept_sec == 3
|
||||||
- item.ansible_job_id is match('\d+\.\d+')
|
# - item.changed == true
|
||||||
with_items: "{{ asyncout.results }}"
|
# - item.ansible_job_id is match('\d+\.\d+')
|
||||||
|
# with_items: "{{ asyncout.results }}"
|
||||||
|
|
||||||
# this part of the test is flaky- Windows PIDs are reused aggressively, so this occasionally fails due to a new process with the same ID
|
# this part of the test is flaky- Windows PIDs are reused aggressively, so this occasionally fails due to a new process with the same ID
|
||||||
# FUTURE: consider having the test module hook to a kernel object we can poke at that gets signaled/released on exit
|
# FUTURE: consider having the test module hook to a kernel object we can poke at that gets signaled/released on exit
|
||||||
|
|
|
@ -4,6 +4,6 @@
|
||||||
- { role: test_win_service, tags: test_win_service }
|
- { role: test_win_service, tags: test_win_service }
|
||||||
- { role: test_win_feature, tags: test_win_feature }
|
- { role: test_win_feature, tags: test_win_feature }
|
||||||
- { role: test_win_user, tags: test_win_user }
|
- { role: test_win_user, tags: test_win_user }
|
||||||
- { role: test_win_async_wrapper, tags: test_win_async_wrapper }
|
- { role: test_win_async_wrapper, tags: ["test_win_async_wrapper","test_async_wrapper","test_win_async_status","test_async_status"] }
|
||||||
- { role: test_win_shell, tags: test_win_shell }
|
- { role: test_win_shell, tags: test_win_shell }
|
||||||
- { role: test_win_command, tags: test_win_command }
|
- { role: test_win_command, tags: test_win_command }
|
||||||
|
|
Loading…
Reference in a new issue